Enhancing extraction rules based on user feedback

ABSTRACT

Embodiments of the present invention are directed to enhancing extraction rules utilizing user feedback. In embodiments, a set of extraction rules relevant to an event set are provided for display. Thereafter, a selection of an extraction rule is received and, in response, a set of events matching the selected extraction rule is provided for display. A modification, for example provided by a user, in association with the extraction rule or the set of events is received. Such a modification is then used (e.g., via machine learning) to enhance extraction rules available for performing subsequent data extraction.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is related to co-pending of U.S. patentapplication Ser. No. 16/264,525 filed Jan. 31, 2019 and titled“EXTRACTION RULE VALIDATION,” which the contents of which areincorporated by reference herein in their entirety.

BACKGROUND

Modern data centers often include thousands of hosts that operatecollectively to service requests from even larger numbers of remoteclients. During operation, components of these data centers can producesignificant volumes of raw, machine-generated data. In many cases,extraction rules are utilized to extract data.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings:

FIG. 1 illustrates a networked computer environment in which anembodiment may be implemented;

FIG. 2 illustrates a block diagram of an example data intake and querysystem in which an embodiment may be implemented;

FIG. 3 is a flow diagram that illustrates how indexers process, index,and store data received from forwarders in accordance with the disclosedembodiments;

FIG. 4 is a flow diagram that illustrates how a search head and indexersperform a search query in accordance with the disclosed embodiments;

FIG. 5 illustrates a scenario where a common customer ID is found amonglog data received from three disparate sources in accordance with thedisclosed embodiments;

FIG. 6A illustrates a search screen in accordance with the disclosedembodiments;

FIG. 6B illustrates a data summary dialog that enables a user to selectvarious data sources in accordance with the disclosed embodiments;

FIGS. 7A-7D illustrate a series of user interface screens for an exampledata model-driven report generation interface in accordance with thedisclosed embodiments;

FIG. 8 illustrates an example search query received from a client andexecuted by search peers in accordance with the disclosed embodiments;

FIG. 9A illustrates a key indicators view in accordance with thedisclosed embodiments;

FIG. 9B illustrates an incident review dashboard in accordance with thedisclosed embodiments;

FIG. 9C illustrates a proactive monitoring tree in accordance with thedisclosed embodiments;

FIG. 9D illustrates a user interface screen displaying both log data andperformance data in accordance with the disclosed embodiments;

FIG. 10 illustrates a block diagram of an example cloud-based dataintake and query system in which an embodiment may be implemented;

FIG. 11 illustrates a block diagram of an example data intake and querysystem that performs searches across external data systems in accordancewith the disclosed embodiments;

FIGS. 12-14 illustrate a series of user interface screens for an exampledata model-driven report generation interface in accordance with thedisclosed embodiments;

FIGS. 15-17 illustrate example visualizations generated by a reportingapplication in accordance with the disclosed embodiments;

FIG. 18 depicts an example data-processing environment in accordancewith various embodiments of the present disclosure;

FIG. 19 provides an illustrative implementation of performing extractionrule enhancement, in accordance with embodiments of the presentdisclosure;

FIGS. 20A-20H depict illustrative user interfaces that may be used tofacilitate enhancement of extraction rules, according to embodiments ofthe present invention;

FIG. 21 illustrates a method of enhancing extraction rules, inaccordance with embodiments of the present invention, according toembodiments of the present invention;

FIG. 22 provides an illustrative implementation of facilitatingvalidation and enhancement of extraction rules, according to embodimentsof the present invention;

FIG. 23 illustrates a method of validating and enhancing extractionrules, in accordance with embodiments of the present invention; and

FIG. 24 is a block diagram of an example computing device in whichembodiments of the present disclosure may be employed.

DETAILED DESCRIPTION

Embodiments are described herein according to the following outline:

-   -   1.0. General Overview    -   2.0. Operating Environment        -   2.1. Host Devices        -   2.2. Client Devices        -   2.3. Client Device Applications        -   2.4. Data Server System        -   2.5. Data Ingestion            -   2.5.1. Input            -   2.5.2. Parsing            -   2.5.3. Indexing        -   2.6. Query Processing        -   2.7. Field Extraction        -   2.8. Example Search Screen        -   2.9. Data Modeling        -   2.10. Acceleration Techniques            -   2.10.1. Aggregation Technique            -   2.10.2. Keyword Index            -   2.10.3. High Performance Analytics Store            -   2.10.4. Accelerating Report Generation        -   2.11. Security Features        -   2.12. Data Center Monitoring        -   2.13. Cloud-Based System Overview        -   2.14. Searching Externally Archived Data            -   2.14.1. ERP Process Features        -   2.15 Cloud-Based Architecture    -   3.0. Overview of Facilitating Extraction Rule Enhancement and        Validation In A Data Processing Environment        -   3.1. Overview of a Field Extraction System in a Data            Processing Environment        -   3.2. Extraction Rule Enhancement via Build-Time            Implementation        -   3.3 Extraction Rule Validation and Enhancement via Run-Time            Implementation        -   3.4. Illustrative Hardware System

1.0 General Overview

Modern data centers and other computing environments can compriseanywhere from a few host computer systems to thousands of systemsconfigured to process data, service requests from remote clients, andperform numerous other computational tasks. During operation, variouscomponents within these computing environments often generatesignificant volumes of machine-generated data. For example, machine datais generated by various components in the information technology (IT)environments, such as servers, sensors, routers, mobile devices,Internet of Things (IoT) devices, etc. Machine-generated data caninclude system logs, network packet data, sensor data, applicationprogram data, error logs, stack traces, system performance data, etc. Ingeneral, machine-generated data can also include performance data,diagnostic information, and many other types of data that can beanalyzed to diagnose performance problems, monitor user interactions,and to derive other insights.

A number of tools are available to analyze machine data, that is,machine-generated data. In order to reduce the size of the potentiallyvast amount of machine data that may be generated, many of these toolstypically pre-process the data based on anticipated data-analysis needs.For example, pre-specified data items may be extracted from the machinedata and stored in a database to facilitate efficient retrieval andanalysis of those data items at search time. However, the rest of themachine data typically is not saved and discarded during pre-processing.As storage capacity becomes progressively cheaper and more plentiful,there are fewer incentives to discard these portions of machine data andmany reasons to retain more of the data.

This plentiful storage capacity is presently making it feasible to storemassive quantities of minimally processed machine data for laterretrieval and analysis. In general, storing minimally processed machinedata and performing analysis operations at search time can providegreater flexibility because it enables an analyst to search all of themachine data, instead of searching only a pre-specified set of dataitems. This may enable an analyst to investigate different aspects ofthe machine data that previously were unavailable for analysis.

However, analyzing and searching massive quantities of machine datapresents a number of challenges. For example, a data center, servers, ornetwork appliances may generate many different types and formats ofmachine data (e.g., system logs, network packet data (e.g., wire data,etc.), sensor data, application program data, error logs, stack traces,system performance data, operating system data, virtualization data,etc.) from thousands of different components, which can collectively bevery time-consuming to analyze. In another example, mobile devices maygenerate large amounts of information relating to data accesses,application performance, operating system performance, networkperformance, etc. There can be millions of mobile devices that reportthese types of information.

These challenges can be addressed by using an event-based data intakeand query system, such as the SPLUNK® ENTERPRISE system developed bySplunk Inc. of San Francisco, California. The SPLUNK® ENTERPRISE systemis the leading platform for providing real-time operational intelligencethat enables organizations to collect, index, and searchmachine-generated data from various websites, applications, servers,networks, and mobile devices that power their businesses. The SPLUNK®ENTERPRISE system is particularly useful for analyzing data which iscommonly found in system log files, network data, and other data inputsources. Although many of the techniques described herein are explainedwith reference to a data intake and query system similar to the SPLUNK®ENTERPRISE system, these techniques are also applicable to other typesof data systems.

In the SPLUNK® ENTERPRISE system, machine-generated data are collectedand stored as “events”. An event comprises a portion of themachine-generated data and is associated with a specific point in time.For example, events may be derived from “time series data,” where thetime series data comprises a sequence of data points (e.g., performancemeasurements from a computer system, etc.) that are associated withsuccessive points in time. In general, each event can be associated witha timestamp that is derived from the raw data in the event, determinedthrough interpolation between temporally proximate events having knowntimestamps, or determined based on other configurable rules forassociating timestamps with events, etc.

In some instances, machine data can have a predefined format, where dataitems with specific data formats are stored at predefined locations inthe data. For example, the machine data may include data stored asfields in a database table. In other instances, machine data may nothave a predefined format, that is, the data is not at fixed, predefinedlocations, but the data does have repeatable patterns and is not random.This means that some machine data can comprise various data items ofdifferent data types and that may be stored at different locationswithin the data. For example, when the data source is an operatingsystem log, an event can include one or more lines from the operatingsystem log containing raw data that includes different types ofperformance and diagnostic information associated with a specific pointin time.

Examples of components which may generate machine data from which eventscan be derived include, but are not limited to, web servers, applicationservers, databases, firewalls, routers, operating systems, and softwareapplications that execute on computer systems, mobile devices, sensors,Internet of Things (IoT) devices, etc. The data generated by such datasources can include, for example and without limitation, server logfiles, activity log files, configuration files, messages, network packetdata, performance measurements, sensor measurements, etc.

The SPLUNK® ENTERPRISE system uses flexible schema to specify how toextract information from the event data. A flexible schema may bedeveloped and redefined as needed. Note that a flexible schema may beapplied to event data “on the fly,” when it is needed (e.g., at searchtime, index time, ingestion time, etc.). When the schema is not appliedto event data until search time it may be referred to as a “late-bindingschema.”

During operation, the SPLUNK® ENTERPRISE system starts with raw inputdata (e.g., one or more system logs, streams of network packet data,sensor data, application program data, error logs, stack traces, systemperformance data, etc.). The system divides this raw data into blocks(e.g., buckets of data, each associated with a specific time frame,etc.), and parses the raw data to produce timestamped events. The systemstores the timestamped events in a data store. The system enables usersto run queries against the stored data to, for example, retrieve eventsthat meet criteria specified in a query, such as containing certainkeywords or having specific values in defined fields. As used hereinthroughout, data that is part of an event is referred to as “eventdata”. In this context, the term “field” refers to a location in theevent data containing one or more values for a specific data item. Aswill be described in more detail herein, the fields are defined byextraction rules (e.g., regular expressions) that derive one or morevalues from the portion of raw machine data in each event that has aparticular field specified by an extraction rule. The set of values soproduced are semantically-related (such as IP address), even though theraw machine data in each event may be in different formats (e.g.,semantically-related values may be in different positions in the eventsderived from different sources).

As noted above, the SPLUNK® ENTERPRISE system utilizes a late-bindingschema to event data while performing queries on events. One aspect of alate-binding schema is applying “extraction rules” to event data toextract values for specific fields during search time. Morespecifically, the extraction rules for a field can include one or moreinstructions that specify how to extract a value for the field from theevent data. An extraction rule can generally include any type ofinstruction for extracting values from data in events. In some cases, anextraction rule comprises a regular expression where a sequence ofcharacters form a search pattern, in which case the rule is referred toas a “regex rule.” The system applies the regex rule to the event datato extract values for associated fields in the event data by searchingthe event data for the sequence of characters defined in the regex rule.

In the SPLUNK® ENTERPRISE system, a field extractor may be configured toautomatically generate extraction rules for certain field values in theevents when the events are being created, indexed, or stored, orpossibly at a later time. Alternatively, a user may manually defineextraction rules for fields using a variety of techniques. In contrastto a conventional schema for a database system, a late-binding schema isnot defined at data ingestion time. Instead, the late-binding schema canbe developed on an ongoing basis until the time a query is actuallyexecuted. This means that extraction rules for the fields in a query maybe provided in the query itself, or may be located during execution ofthe query. Hence, as a user learns more about the data in the events,the user can continue to refine the late-binding schema by adding newfields, deleting fields, or modifying the field extraction rules for usethe next time the schema is used by the system. Because the SPLUNK®ENTERPRISE system maintains the underlying raw data and useslate-binding schema for searching the raw data, it enables a user tocontinue investigating and learn valuable insights about the raw data.

In some embodiments, a common field name may be used to reference two ormore fields containing equivalent data items, even though the fields maybe associated with different types of events that possibly havedifferent data formats and different extraction rules. By enabling acommon field name to be used to identify equivalent fields fromdifferent types of events generated by disparate data sources, thesystem facilitates use of a “common information model” (CIM) across thedisparate data sources (further discussed with respect to FIG. 5 ).

2.0. Operating Environment

FIG. 1 illustrates a networked computer system 100 in which anembodiment may be implemented. Those skilled in the art would understandthat FIG. 1 represents one example of a networked computer system andother embodiments may use different arrangements.

The networked computer system 100 comprises one or more computingdevices. These one or more computing devices comprise any combination ofhardware and software configured to implement the various logicalcomponents described herein. For example, the one or more computingdevices may include one or more memories that store instructions forimplementing the various components described herein, one or morehardware processors configured to execute the instructions stored in theone or more memories, and various data repositories in the one or morememories for storing data structures utilized and manipulated by thevarious components.

In an embodiment, one or more client devices 102 are coupled to one ormore host devices 106 and a data intake and query system 108 via one ormore networks 104. Networks 104 broadly represent one or more LANs,WANs, cellular networks (e.g., LTE, HSPA, 3G, and other cellulartechnologies), and/or networks using any of wired, wireless, terrestrialmicrowave, or satellite links, and may include the public Internet.

2.1. Host Devices

In the illustrated embodiment, a system 100 includes one or more hostdevices 106. Host devices 106 may broadly include any number ofcomputers, virtual machine instances, and/or data centers that areconfigured to host or execute one or more instances of host applications114. In general, a host device 106 may be involved, directly orindirectly, in processing requests received from client devices 102.Each host device 106 may comprise, for example, one or more of a networkdevice, a web server, an application server, a database server, etc. Acollection of host devices 106 may be configured to implement anetwork-based service. For example, a provider of a network-basedservice may configure one or more host devices 106 and host applications114 (e.g., one or more web servers, application servers, databaseservers, etc.) to collectively implement the network-based application.

In general, client devices 102 communicate with one or more hostapplications 114 to exchange information. The communication between aclient device 102 and a host application 114 may, for example, be basedon the Hypertext Transfer Protocol (HTTP) or any other network protocol.Content delivered from the host application 114 to a client device 102may include, for example, HTML documents, media content, etc. Thecommunication between a client device 102 and host application 114 mayinclude sending various requests and receiving data packets. Forexample, in general, a client device 102 or application running on aclient device may initiate communication with a host application 114 bymaking a request for a specific resource (e.g., based on an HTTPrequest), and the application server may respond with the requestedcontent stored in one or more response packets.

In the illustrated embodiment, one or more of host applications 114 maygenerate various types of performance data during operation, includingevent logs, network data, sensor data, and other types ofmachine-generated data. For example, a host application 114 comprising aweb server may generate one or more web server logs in which details ofinteractions between the web server and any number of client devices 102is recorded. As another example, a host device 106 comprising a routermay generate one or more router logs that record information related tonetwork traffic managed by the router. As yet another example, a hostapplication 114 comprising a database server may generate one or morelogs that record information related to requests sent from other hostapplications 114 (e.g., web servers or application servers) for datamanaged by the database server.

2.2. Client Devices

Client devices 102 of FIG. 1 represent any computing device capable ofinteracting with one or more host devices 106 via a network 104.Examples of client devices 102 may include, without limitation, smartphones, tablet computers, handheld computers, wearable devices, laptopcomputers, desktop computers, servers, portable media players, gamingdevices, and so forth. In general, a client device 102 can provideaccess to different content, for instance, content provided by one ormore host devices 106, etc. Each client device 102 may comprise one ormore client applications 110, described in more detail in a separatesection hereinafter.

2.3. Client Device Applications

In an embodiment, each client device 102 may host or execute one or moreclient applications 110 that are capable of interacting with one or morehost devices 106 via one or more networks 104. For instance, a clientapplication 110 may be or comprise a web browser that a user may use tonavigate to one or more websites or other resources provided by one ormore host devices 106. As another example, a client application 110 maycomprise a mobile application or “app.” For example, an operator of anetwork-based service hosted by one or more host devices 106 may makeavailable one or more mobile apps that enable users of client devices102 to access various resources of the network-based service. As yetanother example, client applications 110 may include backgroundprocesses that perform various operations without direct interactionfrom a user. A client application 110 may include a “plug-in” or“extension” to another application, such as a web browser plug-in orextension.

In an embodiment, a client application 110 may include a monitoringcomponent 112. At a high level, the monitoring component 112 comprises asoftware component or other logic that facilitates generatingperformance data related to a client device's operating state, includingmonitoring network traffic sent and received from the client device andcollecting other device and/or application-specific information.Monitoring component 112 may be an integrated component of a clientapplication 110, a plug-in, an extension, or any other type of add-oncomponent. Monitoring component 112 may also be a stand-alone process.

In one embodiment, a monitoring component 112 may be created when aclient application 110 is developed, for example, by an applicationdeveloper using a software development kit (SDK). The SDK may includecustom monitoring code that can be incorporated into the codeimplementing a client application 110. When the code is converted to anexecutable application, the custom code implementing the monitoringfunctionality can become part of the application itself.

In some cases, an SDK or other code for implementing the monitoringfunctionality may be offered by a provider of a data intake and querysystem, such as a system 108. In such cases, the provider of the system108 can implement the custom code so that performance data generated bythe monitoring functionality is sent to the system 108 to facilitateanalysis of the performance data by a developer of the clientapplication or other users.

In an embodiment, the custom monitoring code may be incorporated intothe code of a client application 110 in a number of different ways, suchas the insertion of one or more lines in the client application codethat call or otherwise invoke the monitoring component 112. As such, adeveloper of a client application 110 can add one or more lines of codeinto the client application 110 to trigger the monitoring component 112at desired points during execution of the application. Code thattriggers the monitoring component may be referred to as a monitortrigger. For instance, a monitor trigger may be included at or near thebeginning of the executable code of the client application 110 such thatthe monitoring component 112 is initiated or triggered as theapplication is launched, or included at other points in the code thatcorrespond to various actions of the client application, such as sendinga network request or displaying a particular interface.

In an embodiment, the monitoring component 112 may monitor one or moreaspects of network traffic sent and/or received by a client application110. For example, the monitoring component 112 may be configured tomonitor data packets transmitted to and/or from one or more hostapplications 114. Incoming and/or outgoing data packets can be read orexamined to identify network data contained within the packets, forexample, and other aspects of data packets can be analyzed to determinea number of network performance statistics. Monitoring network trafficmay enable information to be gathered particular to the networkperformance associated with a client application 110 or set ofapplications.

In an embodiment, network performance data refers to any type of datathat indicates information about the network and/or network performanceNetwork performance data may include, for instance, a URL requested, aconnection type (e.g., HTTP, HTTPS, etc.), a connection start time, aconnection end time, an HTTP status code, request length, responselength, request headers, response headers, connection status (e.g.,completion, response time(s), failure, etc.), and the like. Uponobtaining network performance data indicating performance of thenetwork, the network performance data can be transmitted to a dataintake and query system 108 for analysis.

Upon developing a client application 110 that incorporates a monitoringcomponent 112, the client application 110 can be distributed to clientdevices 102. Applications generally can be distributed to client devices102 in any manner, or they can be pre-loaded. In some cases, theapplication may be distributed to a client device 102 via an applicationmarketplace or other application distribution system. For instance, anapplication marketplace or other application distribution system mightdistribute the application to a client device based on a request fromthe client device to download the application.

Examples of functionality that enables monitoring performance of aclient device are described in U.S. patent application Ser. No.14/524,748, entitled “UTILIZING PACKET HEADERS TO MONITOR NETWORKTRAFFIC IN ASSOCIATION WITH A CLIENT DEVICE”, filed on 27 Oct. 2014, andwhich is hereby incorporated by reference in its entirety for allpurposes.

In an embodiment, the monitoring component 112 may also monitor andcollect performance data related to one or more aspects of theoperational state of a client application 110 and/or client device 102.For example, a monitoring component 112 may be configured to collectdevice performance information by monitoring one or more client deviceoperations, or by making calls to an operating system and/or one or moreother applications executing on a client device 102 for performanceinformation. Device performance information may include, for instance, acurrent wireless signal strength of the device, a current connectiontype and network carrier, current memory performance information, ageographic location of the device, a device orientation, and any otherinformation related to the operational state of the client device.

In an embodiment, the monitoring component 112 may also monitor andcollect other device profile information including, for example, a typeof client device, a manufacturer and model of the device, versions ofvarious software applications installed on the device, and so forth.

In general, a monitoring component 112 may be configured to generateperformance data in response to a monitor trigger in the code of aclient application 110 or other triggering application event, asdescribed above, and to store the performance data in one or more datarecords. Each data record, for example, may include a collection offield-value pairs, each field-value pair storing a particular item ofperformance data in association with a field for the item. For example,a data record generated by a monitoring component 112 may include a“networkLatency” field (not shown in the Figure) in which a value isstored. This field indicates a network latency measurement associatedwith one or more network requests. The data record may include a “state”field to store a value indicating a state of a network connection, andso forth for any number of aspects of collected performance data.

2.4. Data Server System

FIG. 2 depicts a block diagram of an exemplary data intake and querysystem 108, similar to the SPLUNK® ENTERPRISE system. System 108includes one or more forwarders 204 that receive data from a variety ofinput data sources 202, and one or more indexers 206 that process andstore the data in one or more data stores 208. These forwarders andindexers can comprise separate computer systems, or may alternativelycomprise separate processes executing on one or more computer systems.

Each data source 202 broadly represents a distinct source of data thatcan be consumed by a system 108. Examples of a data source 202 include,without limitation, data files, directories of files, data sent over anetwork, event logs, registries, etc.

During operation, the forwarders 204 identify which indexers 206 receivedata collected from a data source 202 and forward the data to theappropriate indexers. Forwarders 204 can also perform operations on thedata before forwarding, including removing extraneous data, detectingtimestamps in the data, parsing data, indexing data, routing data basedon criteria relating to the data being routed, and/or performing otherdata transformations.

In an embodiment, a forwarder 204 may comprise a service accessible toclient devices 102 and host devices 106 via a network 104. For example,one type of forwarder 204 may be capable of consuming vast amounts ofreal-time data from a potentially large number of client devices 102and/or host devices 106. The forwarder 204 may, for example, comprise acomputing device which implements multiple data pipelines or “queues” tohandle forwarding of network data to indexers 206. A forwarder 204 mayalso perform many of the functions that are performed by an indexer. Forexample, a forwarder 204 may perform keyword extractions on raw data orparse raw data to create events. A forwarder 204 may generate timestamps for events. Additionally or alternatively, a forwarder 204 mayperform routing of events to indexers. Data store 208 may contain eventsderived from machine data from a variety of sources all pertaining tothe same component in an IT environment, and this data may be producedby the machine in question or by other components in the IT environment.

2.5. Data Ingestion

FIG. 3 depicts a flow chart illustrating an example data flow performedby Data Intake and Query system 108, in accordance with the disclosedembodiments. The data flow illustrated in FIG. 3 is provided forillustrative purposes only; those skilled in the art would understandthat one or more of the steps of the processes illustrated in FIG. 3 maybe removed or the ordering of the steps may be changed. Furthermore, forthe purposes of illustrating a clear example, one or more particularsystem components are described in the context of performing variousoperations during each of the data flow stages. For example, a forwarderis described as receiving and processing data during an input phase; anindexer is described as parsing and indexing data during parsing andindexing phases; and a search head is described as performing a searchquery during a search phase. However, other system arrangements anddistributions of the processing steps across system components may beused.

2.5.1. Input

At block 302, a forwarder receives data from an input source, such as adata source 202 shown in FIG. 2 . A forwarder initially may receive thedata as a raw data stream generated by the input source. For example, aforwarder may receive a data stream from a log file generated by anapplication server, from a stream of network data from a network device,or from any other source of data. In one embodiment, a forwarderreceives the raw data and may segment the data stream into “blocks”, or“buckets,” possibly of a uniform data size, to facilitate subsequentprocessing steps.

At block 304, a forwarder or other system component annotates each blockgenerated from the raw data with one or more metadata fields. Thesemetadata fields may, for example, provide information related to thedata block as a whole and may apply to each event that is subsequentlyderived from the data in the data block. For example, the metadatafields may include separate fields specifying each of a host, a source,and a source type related to the data block. A host field may contain avalue identifying a host name or IP address of a device that generatedthe data. A source field may contain a value identifying a source of thedata, such as a pathname of a file or a protocol and port related toreceived network data. A source type field may contain a valuespecifying a particular source type label for the data. Additionalmetadata fields may also be included during the input phase, such as acharacter encoding of the data, if known, and possibly other values thatprovide information relevant to later processing steps. In anembodiment, a forwarder forwards the annotated data blocks to anothersystem component (typically an indexer) for further processing.

The SPLUNK® ENTERPRISE system allows forwarding of data from one SPLUNK®ENTERPRISE instance to another, or even to a third-party system. SPLUNK®ENTERPRISE system can employ different types of forwarders in aconfiguration.

In an embodiment, a forwarder may contain the essential componentsneeded to forward data. It can gather data from a variety of inputs andforward the data to a SPLUNK® ENTERPRISE server for indexing andsearching. It also can tag metadata (e.g., source, source type, host,etc.).

Additionally or optionally, in an embodiment, a forwarder has thecapabilities of the aforementioned forwarder as well as additionalcapabilities. The forwarder can parse data before forwarding the data(e.g., associate a time stamp with a portion of data and create anevent, etc.) and can route data based on criteria such as source or typeof event. It can also index data locally while forwarding the data toanother indexer.

2.5.2. Parsing

At block 306, an indexer receives data blocks from a forwarder andparses the data to organize the data into events. In an embodiment, toorganize the data into events, an indexer may determine a source typeassociated with each data block (e.g., by extracting a source type labelfrom the metadata fields associated with the data block, etc.) and referto a source type configuration corresponding to the identified sourcetype. The source type definition may include one or more properties thatindicate to the indexer to automatically determine the boundaries ofevents within the data. In general, these properties may include regularexpression-based rules or delimiter rules where, for example, eventboundaries may be indicated by predefined characters or characterstrings. These predefined characters may include punctuation marks orother special characters including, for example, carriage returns, tabs,spaces, line breaks, etc. If a source type for the data is unknown tothe indexer, an indexer may infer a source type for the data byexamining the structure of the data. Then, it can apply an inferredsource type definition to the data to create the events.

At block 308, the indexer determines a timestamp for each event. Similarto the process for creating events, an indexer may again refer to asource type definition associated with the data to locate one or moreproperties that indicate instructions for determining a timestamp foreach event. The properties may, for example, instruct an indexer toextract a time value from a portion of data in the event, to interpolatetime values based on timestamps associated with temporally proximateevents, to create a timestamp based on a time the event data wasreceived or generated, to use the timestamp of a previous event, or useany other rules for determining timestamps.

At block 310, the indexer associates with each event one or moremetadata fields including a field containing the timestamp (in someembodiments, a timestamp may be included in the metadata fields)determined for the event. These metadata fields may include a number of“default fields” that are associated with all events, and may alsoinclude one more custom fields as defined by a user. Similar to themetadata fields associated with the data blocks at block 304, thedefault metadata fields associated with each event may include a host,source, and source type field including or in addition to a fieldstoring the timestamp.

At block 312, an indexer may optionally apply one or moretransformations to data included in the events created at block 306. Forexample, such transformations can include removing a portion of an event(e.g., a portion used to define event boundaries, extraneous charactersfrom the event, other extraneous text, etc.), masking a portion of anevent (e.g., masking a credit card number), removing redundant portionsof an event, etc. The transformations applied to event data may, forexample, be specified in one or more configuration files and referencedby one or more source type definitions.

2.5.3. Indexing

At blocks 314 and 316, an indexer can optionally generate a keywordindex to facilitate fast keyword searching for event data. To build akeyword index, at block 314, the indexer identifies a set of keywords ineach event. At block 316, the indexer includes the identified keywordsin an index, which associates each stored keyword with referencepointers to events containing that keyword (or to locations withinevents where that keyword is located, other location identifiers, etc.).When an indexer subsequently receives a keyword-based query, the indexercan access the keyword index to quickly identify events containing thekeyword.

In some embodiments, the keyword index may include entries forname-value pairs found in events, where a name-value pair can include apair of keywords connected by a symbol, such as an equals sign or colon.This way, events containing these name-value pairs can be quicklylocated. In some embodiments, fields can automatically be generated forsome or all of the name-value pairs at the time of indexing. Forexample, if the string “dest=10.0.1.2” is found in an event, a fieldnamed “dest” may be created for the event, and assigned a value of“10.0.1.2”.

At block 318, the indexer stores the events with an associated timestampin a data store 208. Timestamps enable a user to search for events basedon a time range. In one embodiment, the stored events are organized into“buckets,” where each bucket stores events associated with a specifictime range based on the timestamps associated with each event. This maynot only improve time-based searching, but also allows for events withrecent timestamps, which may have a higher likelihood of being accessed,to be stored in a faster memory to facilitate faster retrieval. Forexample, buckets containing the most recent events can be stored inflash memory rather than on a hard disk.

Each indexer 206 may be responsible for storing and searching a subsetof the events contained in a corresponding data store 208. Bydistributing events among the indexers and data stores, the indexers cananalyze events for a query in parallel. For example, using map-reducetechniques, each indexer returns partial responses for a subset ofevents to a search head that combines the results to produce an answerfor the query. By storing events in buckets for specific time ranges, anindexer may further optimize data retrieval process by searching bucketscorresponding to time ranges that are relevant to a query.

Moreover, events and buckets can also be replicated across differentindexers and data stores to facilitate high availability and disasterrecovery as described in U.S. patent application Ser. No. 14/266,812,entitled “SITE-BASED SEARCH AFFINITY”, filed on 30 Apr. 2014, and inU.S. patent application Ser. No. 14/266,817, entitled “MULTI-SITECLUSTERING”, also filed on 30 Apr. 2014, each of which is herebyincorporated by reference in its entirety for all purposes.

2.6. Query Processing

FIG. 4 is a flow diagram that illustrates an exemplary process that asearch head and one or more indexers may perform during a search query.At block 402, a search head receives a search query from a client. Atblock 404, the search head analyzes the search query to determine whatportion(s) of the query can be delegated to indexers and what portionsof the query can be executed locally by the search head. At block 406,the search head distributes the determined portions of the query to theappropriate indexers. In an embodiment, a search head cluster may takethe place of an independent search head where each search head in thesearch head cluster coordinates with peer search heads in the searchhead cluster to schedule jobs, replicate search results, updateconfigurations, fulfill search requests, etc. In an embodiment, thesearch head (or each search head) communicates with a master node (alsoknown as a cluster master, not shown in Fig.) that provides the searchhead with a list of indexers to which the search head can distribute thedetermined portions of the query. The master node maintains a list ofactive indexers and can also designate which indexers may haveresponsibility for responding to queries over certain sets of events. Asearch head may communicate with the master node before the search headdistributes queries to indexers to discover the addresses of activeindexers.

At block 408, the indexers to which the query was distributed, searchdata stores associated with them for events that are responsive to thequery. To determine which events are responsive to the query, theindexer searches for events that match the criteria specified in thequery. These criteria can include matching keywords or specific valuesfor certain fields. The searching operations at block 408 may use thelate-binding schema to extract values for specified fields from eventsat the time the query is processed. In an embodiment, one or more rulesfor extracting field values may be specified as part of a source typedefinition. The indexers may then either send the relevant events backto the search head, or use the events to determine a partial result, andsend the partial result back to the search head.

At block 410, the search head combines the partial results and/or eventsreceived from the indexers to produce a final result for the query. Thisfinal result may comprise different types of data depending on what thequery requested. For example, the results can include a listing ofmatching events returned by the query, or some type of visualization ofthe data from the returned events. In another example, the final resultcan include one or more calculated values derived from the matchingevents.

The results generated by the system 108 can be returned to a clientusing different techniques. For example, one technique streams resultsor relevant events back to a client in real-time as they are identified.Another technique waits to report the results to the client until acomplete set of results (which may include a set of relevant events or aresult based on relevant events) is ready to return to the client. Yetanother technique streams interim results or relevant events back to theclient in real-time until a complete set of results is ready, and thenreturns the complete set of results to the client. In another technique,certain results are stored as “search jobs” and the client may retrievethe results by referring the search jobs.

The search head can also perform various operations to make the searchmore efficient. For example, before the search head begins execution ofa query, the search head can determine a time range for the query and aset of common keywords that all matching events include. The search headmay then use these parameters to query the indexers to obtain a supersetof the eventual results. Then, during a filtering stage, the search headcan perform field-extraction operations on the superset to produce areduced set of search results. This speeds up queries that are performedon a periodic basis.

2.7. Field Extraction

The search head 210 allows users to search and visualize event dataextracted from raw machine data received from homogenous data sources.It also allows users to search and visualize event data extracted fromraw machine data received from heterogeneous data sources. The searchhead 210 includes various mechanisms, which may additionally reside inan indexer 206, for processing a query. Splunk Processing Language(SPL), used in conjunction with the SPLUNK® ENTERPRISE system, can beutilized to make a query. SPL is a pipelined search language in which aset of inputs is operated on by a first command in a command line, andthen a subsequent command following the pipe symbol “I” operates on theresults produced by the first command, and so on for additional commandsOther query languages, such as the Structured Query Language (“SQL”),can be used to create a query.

In response to receiving the search query, search head 210 usesextraction rules to extract values for the fields associated with afield or fields in the event data being searched. The search head 210obtains extraction rules that specify how to extract a value for certainfields from an event. Extraction rules can comprise regex rules thatspecify how to extract values for the relevant fields. In addition tospecifying how to extract field values, the extraction rules may alsoinclude instructions for deriving a field value by performing a functionon a character string or value retrieved by the extraction rule. Forexample, a transformation rule may truncate a character string, orconvert the character string into a different data format. In somecases, the query itself can specify one or more extraction rules.

The search head 210 can apply the extraction rules to event data that itreceives from indexers 206. Indexers 206 may apply the extraction rulesto events in an associated data store 208. Extraction rules can beapplied to all the events in a data store, or to a subset of the eventsthat have been filtered based on some criteria (e.g., event time stampvalues, etc.). Extraction rules can be used to extract one or morevalues for a field from events by parsing the event data and examiningthe event data for one or more patterns of characters, numbers,delimiters, etc., that indicate where the field begins and, optionally,ends.

FIG. 5 illustrates an example of raw machine data received fromdisparate data sources. In this example, a user submits an order formerchandise using a vendor's shopping application program 501 running onthe user's system. In this example, the order was not delivered to thevendor's server due to a resource exception at the destination serverthat is detected by the middleware code 502. The user then sends amessage to the customer support 503 to complain about the order failingto complete. The three systems 501, 502, and 503 are disparate systemsthat do not have a common logging format. The order application 501sends log data 504 to the SPLUNK® ENTERPRISE system in one format, themiddleware code 502 sends error log data 505 in a second format, and thesupport server 503 sends log data 506 in a third format.

Using the log data received at one or more indexers 206 from the threesystems the vendor can uniquely obtain an insight into user activity,user experience, and system behavior. The search head 210 allows thevendor's administrator to search the log data from the three systemsthat one or more indexers 206 are responsible for searching, therebyobtaining correlated information, such as the order number andcorresponding customer ID number of the person placing the order. Thesystem also allows the administrator to see a visualization of relatedevents via a user interface. The administrator can query the search head210 for customer ID field value matches across the log data from thethree systems that are stored at the one or more indexers 206. Thecustomer ID field value exists in the data gathered from the threesystems, but the customer ID field value may be located in differentareas of the data given differences in the architecture of thesystems—there is a semantic relationship between the customer ID fieldvalues generated by the three systems. The search head 210 requestsevent data from the one or more indexers 206 to gather relevant eventdata from the three systems. It then applies extraction rules to theevent data in order to extract field values that it can correlate. Thesearch head may apply a different extraction rule to each set of eventsfrom each system when the event data format differs among systems. Inthis example, the user interface can display to the administrator theevent data corresponding to the common customer ID field values 507,508, and 509, thereby providing the administrator with insight into acustomer's experience.

Note that query results can be returned to a client, a search head, orany other system component for further processing. In general, queryresults may include a set of one or more events, a set of one or morevalues obtained from the events, a subset of the values, statisticscalculated based on the values, a report containing the values, or avisualization, such as a graph or chart, generated from the values.

2.8. Example Search Screen

FIG. 6A illustrates an example search screen 600 in accordance with thedisclosed embodiments. Search screen 600 includes a search bar 602 thataccepts user input in the form of a search string. It also includes atime range picker 612 that enables the user to specify a time range forthe search. For “historical searches” the user can select a specifictime range, or alternatively a relative time range, such as “today,”“yesterday” or “last week.” For “real-time searches,” the user canselect the size of a preceding time window to search for real-timeevents. Search screen 600 also initially displays a “data summary”dialog as is illustrated in FIG. 6B that enables the user to selectdifferent sources for the event data, such as by selecting specifichosts and log files.

After the search is executed, the search screen 600 in FIG. 6A candisplay the results through search results tabs 604, wherein searchresults tabs 604 includes: an “events tab” that displays variousinformation about events returned by the search; a “statistics tab” thatdisplays statistics about the search results; and a “visualization tab”that displays various visualizations of the search results. The eventstab illustrated in FIG. 6A displays a timeline graph 605 thatgraphically illustrates the number of events that occurred in one-hourintervals over the selected time range. It also displays an events list608 that enables a user to view the raw data in each of the returnedevents. It additionally displays a fields sidebar 606 that includesstatistics about occurrences of specific fields in the returned events,including “selected fields” that are pre-selected by the user, and“interesting fields” that are automatically selected by the system basedon pre-specified criteria.

2.9. Data Models

A data model is a hierarchically structured search-time mapping ofsemantic knowledge about one or more datasets. It encodes the domainknowledge necessary to build a variety of specialized searches of thosedatasets. Those searches, in turn, can be used to generate reports.

A data model is composed of one or more “objects” (or “data modelobjects”) that define or otherwise correspond to a specific set of data.

Objects in data models can be arranged hierarchically in parent/childrelationships. Each child object represents a subset of the datasetcovered by its parent object. The top-level objects in data models arecollectively referred to as “root objects.”

Child objects have inheritance. Data model objects are defined bycharacteristics that mostly break down into constraints and attributes.Child objects inherit constraints and attributes from their parentobjects and have additional constraints and attributes of their own.Child objects provide a way of filtering events from parent objects.Because a child object always provides an additional constraint inaddition to the constraints it has inherited from its parent object, thedataset it represents is always a subset of the dataset that its parentrepresents.

For example, a first data model object may define a broad set of datapertaining to e-mail activity generally, and another data model objectmay define specific datasets within the broad dataset, such as a subsetof the e-mail data pertaining specifically to e-mails sent. Examples ofdata models can include electronic mail, authentication, databases,intrusion detection, malware, application state, alerts, computeinventory, network sessions, network traffic, performance, audits,updates, vulnerabilities, etc. Data models and their objects can bedesigned by knowledge managers in an organization, and they can enabledownstream users to quickly focus on a specific set of data. Forexample, a user can simply select an “e-mail activity” data model objectto access a dataset relating to e-mails generally (e.g., sent orreceived), or select an “e-mails sent” data model object (or datasub-model object) to access a dataset relating to e-mails sent.

A data model object may be defined by (1) a set of search constraints,and (2) a set of fields. Thus, a data model object can be used toquickly search data to identify a set of events and to identify a set offields to be associated with the set of events. For example, an “e-mailssent” data model object may specify a search for events relating toe-mails that have been sent, and specify a set of fields that areassociated with the events. Thus, a user can retrieve and use the“e-mails sent” data model object to quickly search source data forevents relating to sent e-mails, and may be provided with a listing ofthe set of fields relevant to the events in a user interface screen.

A child of the parent data model may be defined by a search (typically anarrower search) that produces a subset of the events that would beproduced by the parent data model's search. The child's set of fieldscan include a subset of the set of fields of the parent data modeland/or additional fields. Data model objects that reference the subsetscan be arranged in a hierarchical manner, so that child subsets ofevents are proper subsets of their parents. A user iteratively applies amodel development tool (not shown in Fig.) to prepare a query thatdefines a subset of events and assigns an object name to that subset. Achild subset is created by further limiting a query that generated aparent subset. A late-binding schema of field extraction rules isassociated with each object or subset in the data model.

Data definitions in associated schemas can be taken from the commoninformation model (CIM) or can be devised for a particular schema andoptionally added to the CIM. Child objects inherit fields from parentsand can include fields not present in parents. A model developer canselect fewer extraction rules than are available for the sourcesreturned by the query that defines events belonging to a model.Selecting a limited set of extraction rules can be a tool forsimplifying and focusing the data model, while allowing a userflexibility to explore the data subset. Development of a data model isfurther explained in U.S. Pat. Nos. 8,788,525 and 8,788,526, bothentitled “DATA MODEL FOR MACHINE DATA FOR SEMANTIC SEARCH”, both issuedon 22 Jul. 2014, U.S. Pat. No. 8,983,994, entitled “GENERATION OF A DATAMODEL FOR SEARCHING MACHINE DATA”, issued on 17 March, 2015, U.S. patentapplication Ser. No. 14/611,232, entitled “GENERATION OF A DATA MODELAPPLIED TO QUERIES”, filed on 31 Jan. 2015, and U.S. patent applicationSer. No. 14/815,884, entitled “GENERATION OF A DATA MODEL APPLIED TOOBJECT QUERIES”, filed on 31 Jul. 2015, each of which is herebyincorporated by reference in its entirety for all purposes. See, also,Knowledge Manager Manual, Build a Data Model, Splunk Enterprise 6.1.3pp. 150-204 (Aug. 25, 2014).

A data model can also include reports. One or more report formats can beassociated with a particular data model and be made available to runagainst the data model. A user can use child objects to design reportswith object datasets that already have extraneous data pre-filtered out.In an embodiment, the data intake and query system 108 provides the userwith the ability to produce reports (e.g., a table, chart,visualization, etc.) without having to enter SPL, SQL, or other querylanguage terms into a search screen. Data models are used as the basisfor the search feature.

Data models may be selected in a report generation interface. The reportgenerator supports drag-and-drop organization of fields to be summarizedin a report. When a model is selected, the fields with availableextraction rules are made available for use in the report. The user mayrefine and/or filter search results to produce more precise reports. Theuser may select some fields for organizing the report and select otherfields for providing detail according to the report organization. Forexample, “region” and “salesperson” are fields used for organizing thereport and sales data can be summarized (subtotaled and totaled) withinthis organization. The report generator allows the user to specify oneor more fields within events and apply statistical analysis on valuesextracted from the specified one or more fields. The report generatormay aggregate search results across sets of events and generatestatistics based on aggregated search results. Building reports usingthe report generation interface is further explained in U.S. patentapplication Ser. No. 14/503,335, entitled “GENERATING REPORTS FROMUNSTRUCTURED DATA”, filed on 30 Sep. 2014, and which is herebyincorporated by reference in its entirety for all purposes, and in PivotManual, Splunk Enterprise 6.1.3 (Aug. 4, 2014). Data visualizations alsocan be generated in a variety of formats, by reference to the datamodel. Reports, data visualizations, and data model objects can be savedand associated with the data model for future use. The data model objectmay be used to perform searches of other data.

FIGS. 12, 13, and 7A-7D illustrate a series of user interface screenswhere a user may select report generation options using data models. Thereport generation process may be driven by a predefined data modelobject, such as a data model object defined and/or saved via a reportingapplication or a data model object obtained from another source. A usercan load a saved data model object using a report editor. For example,the initial search query and fields used to drive the report editor maybe obtained from a data model object. The data model object that is usedto drive a report generation process may define a search and a set offields. Upon loading of the data model object, the report generationprocess may enable a user to use the fields (e.g., the fields defined bythe data model object) to define criteria for a report (e.g., filters,split rows/columns, aggregates, etc.) and the search may be used toidentify events (e.g., to identify events responsive to the search) usedto generate the report. That is, for example, if a data model object isselected to drive a report editor, the graphical user interface of thereport editor may enable a user to define reporting criteria for thereport using the fields associated with the selected data model object,and the events used to generate the report may be constrained to theevents that match, or otherwise satisfy, the search constraints of theselected data model object.

The selection of a data model object for use in driving a reportgeneration may be facilitated by a data model object selectioninterface. FIG. 12 illustrates an example interactive data modelselection graphical user interface 1200 of a report editor that displaysa listing of available data models 1201. The user may select one of thedata models 1202.

FIG. 13 illustrates an example data model object selection graphicaluser interface 1300 that displays available data objects 1301 for theselected data object model 1202. The user may select one of thedisplayed data model objects 1302 for use in driving the reportgeneration process.

Once a data model object is selected by the user, a user interfacescreen 700 shown in FIG. 7A may display an interactive listing ofautomatic field identification options 701 based on the selected datamodel object. For example, a user may select one of the threeillustrated options (e.g., the “All Fields” option 702, the “SelectedFields” option 703, or the “Coverage” option (e.g., fields with at leasta specified % of coverage) 704). If the user selects the “All Fields”option 702, all of the fields identified from the events that werereturned in response to an initial search query may be selected. Thatis, for example, all of the fields of the identified data model objectfields may be selected. If the user selects the “Selected Fields” option703, only the fields from the fields of the identified data model objectfields that are selected by the user may be used. If the user selectsthe “Coverage” option 704, only the fields of the identified data modelobject fields meeting a specified coverage criteria may be selected. Apercent coverage may refer to the percentage of events returned by theinitial search query that a given field appears in. Thus, for example,if an object dataset includes 10,000 events returned in response to aninitial search query, and the “avg_age” field appears in 854 of those10,000 events, then the “avg_age” field would have a coverage of 8.54%for that object dataset. If, for example, the user selects the“Coverage” option and specifies a coverage value of 2%, only fieldshaving a coverage value equal to or greater than 2% may be selected. Thenumber of fields corresponding to each selectable option may bedisplayed in association with each option. For example, “97” displayednext to the “All Fields” option 702 indicates that 97 fields will beselected if the “All Fields” option is selected. The “3” displayed nextto the “Selected Fields” option 703 indicates that 3 of the 97 fieldswill be selected if the “Selected Fields” option is selected. The “49”displayed next to the “Coverage” option 704 indicates that 49 of the 97fields (e.g., the 49 fields having a coverage of 2% or greater) will beselected if the “Coverage” option is selected. The number of fieldscorresponding to the “Coverage” option may be dynamically updated basedon the specified percent of coverage.

FIG. 7B illustrates an example graphical user interface screen (alsocalled the pivot interface) 705 displaying the reporting application's“Report Editor” page. The screen may display interactive elements fordefining various elements of a report. For example, the page includes a“Filters” element 706, a “Split Rows” element 707, a “Split Columns”element 708, and a “Column Values” element 709. The page may include alist of search results 711. In this example, the Split Rows element 707is expanded, revealing a listing of fields 710 that can be used todefine additional criteria (e.g., reporting criteria). The listing offields 710 may correspond to the selected fields (attributes). That is,the listing of fields 710 may list only the fields previously selected,either automatically and/or manually by a user. FIG. 7C illustrates aformatting dialogue 712 that may be displayed upon selecting a fieldfrom the listing of fields 710. The dialogue can be used to format thedisplay of the results of the selection (e.g., label the column to bedisplayed as “component”).

FIG. 7D illustrates an example graphical user interface screen 705including a table of results 713 based on the selected criteriaincluding splitting the rows by the “component” field. A column 714having an associated count for each component listed in the table may bedisplayed that indicates an aggregate count of the number of times thatthe particular field-value pair (e.g., the value in a row) occurs in theset of events responsive to the initial search query.

FIG. 14 illustrates an example graphical user interface screen 1400 thatallows the user to filter search results and to perform statisticalanalysis on values extracted from specific fields in the set of events.In this example, the top ten product names ranked by price are selectedas a filter 1401 that causes the display of the ten most popularproducts sorted by price. Each row is displayed by product name andprice 1402. This results in each product displayed in a column labeled“product name” along with an associated price in a column labeled“price” 1406. Statistical analysis of other fields in the eventsassociated with the ten most popular products have been specified ascolumn values 1403. A count of the number of successful purchases foreach product is displayed in column 1404. These statistics may beproduced by filtering the search results by the product name, findingall occurrences of a successful purchase in a field within the eventsand generating a total of the number of occurrences. A sum of the totalsales is displayed in column 1405, which is a result of themultiplication of the price and the number of successful purchases foreach product.

The reporting application allows the user to create graphicalvisualizations of the statistics generated for a report. For example,FIG. 15 illustrates an example graphical user interface 1500 thatdisplays a set of components and associated statistics 1501. Thereporting application allows the user to select a visualization of thestatistics in a graph (e.g., bar chart, scatter plot, area chart, linechart, pie chart, radial gauge, marker gauge, filler gauge, etc.). FIG.16 illustrates an example of a bar chart visualization 1600 of an aspectof the statistical data 1501. FIG. 17 illustrates a scatter plotvisualization 1700 of an aspect of the statistical data 1501.

2.10. Acceleration Technique

The above-described system provides significant flexibility by enablinga user to analyze massive quantities of minimally processed data “on thefly” at search time instead of storing pre-specified portions of thedata in a database at ingestion time. This flexibility enables a user tosee valuable insights, correlate data, and perform subsequent queries toexamine interesting aspects of the data that may not have been apparentat ingestion time.

However, performing extraction and analysis operations at search timecan involve a large amount of data and require a large number ofcomputational operations, which can cause delays in processing thequeries. Advantageously, SPLUNK® ENTERPRISE system employs a number ofunique acceleration techniques that have been developed to speed upanalysis operations performed at search time. These techniques include:(1) performing search operations in parallel across multiple indexers;(2) using a keyword index; (3) using a high performance analytics store;and (4) accelerating the process of generating reports. These noveltechniques are described in more detail below.

2.10.1. Aggregation Technique

To facilitate faster query processing, a query can be structured suchthat multiple indexers perform the query in parallel, while aggregationof search results from the multiple indexers is performed locally at thesearch head. For example, FIG. 8 illustrates how a search query 802received from a client at a search head 210 can split into two phases,including: (1) subtasks 804 (e.g., data retrieval or simple filtering)that may be performed in parallel by indexers 206 for execution, and (2)a search results aggregation operation 806 to be executed by the searchhead when the results are ultimately collected from the indexers.

During operation, upon receiving search query 802, a search head 210determines that a portion of the operations involved with the searchquery may be performed locally by the search head. The search headmodifies search query 802 by substituting “stats” (create aggregatestatistics over results sets received from the indexers at the searchhead) with “prestats” (create statistics by the indexer from localresults set) to produce search query 804, and then distributes searchquery 804 to distributed indexers, which are also referred to as “searchpeers.” Note that search queries may generally specify search criteriaor operations to be performed on events that meet the search criteria.Search queries may also specify field names, as well as search criteriafor the values in the fields or operations to be performed on the valuesin the fields. Moreover, the search head may distribute the full searchquery to the search peers as illustrated in FIG. 4 , or mayalternatively distribute a modified version (e.g., a more restrictedversion) of the search query to the search peers. In this example, theindexers are responsible for producing the results and sending them tothe search head. After the indexers return the results to the searchhead, the search head aggregates the received results 806 to form asingle search result set. By executing the query in this manner, thesystem effectively distributes the computational operations across theindexers while minimizing data transfers.

2.10.2. Keyword Index

As described above with reference to the flow charts in FIG. 3 and FIG.4 , data intake and query system 108 can construct and maintain one ormore keyword indices to quickly identify events containing specifickeywords. This technique can greatly speed up the processing of queriesinvolving specific keywords. As mentioned above, to build a keywordindex, an indexer first identifies a set of keywords. Then, the indexerincludes the identified keywords in an index, which associates eachstored keyword with references to events containing that keyword, or tolocations within events where that keyword is located. When an indexersubsequently receives a keyword-based query, the indexer can access thekeyword index to quickly identify events containing the keyword.

2.10.3. High Performance Analytics Store

To speed up certain types of queries, some embodiments of system 108create a high performance analytics store, which is referred to as a“summarization table,” that contains entries for specific field-valuepairs. Each of these entries keeps track of instances of a specificvalue in a specific field in the event data and includes references toevents containing the specific value in the specific field. For example,an example entry in a summarization table can keep track of occurrencesof the value “94107” in a “ZIP code” field of a set of events and theentry includes references to all of the events that contain the value“94107” in the ZIP code field. This optimization technique enables thesystem to quickly process queries that seek to determine how many eventshave a particular value for a particular field. To this end, the systemcan examine the entry in the summarization table to count instances ofthe specific value in the field without having to go through theindividual events or perform data extractions at search time. Also, ifthe system needs to process all events that have a specific field-valuecombination, the system can use the references in the summarizationtable entry to directly access the events to extract further informationwithout having to search all of the events to find the specificfield-value combination at search time.

In some embodiments, the system maintains a separate summarization tablefor each of the above-described time-specific buckets that stores eventsfor a specific time range. A bucket-specific summarization tableincludes entries for specific field-value combinations that occur inevents in the specific bucket. Alternatively, the system can maintain aseparate summarization table for each indexer. The indexer-specificsummarization table includes entries for the events in a data store thatare managed by the specific indexer. Indexer-specific summarizationtables may also be bucket-specific.

The summarization table can be populated by running a periodic querythat scans a set of events to find instances of a specific field-valuecombination, or alternatively instances of all field-value combinationsfor a specific field. A periodic query can be initiated by a user, orcan be scheduled to occur automatically at specific time intervals. Aperiodic query can also be automatically launched in response to a querythat asks for a specific field-value combination.

In some cases, when the summarization tables may not cover all of theevents that are relevant to a query, the system can use thesummarization tables to obtain partial results for the events that arecovered by summarization tables, but may also have to search throughother events that are not covered by the summarization tables to produceadditional results. These additional results can then be combined withthe partial results to produce a final set of results for the query. Thesummarization table and associated techniques are described in moredetail in U.S. Pat. No. 8,682,925, entitled “DISTRIBUTED HIGHPERFORMANCE ANALYTICS STORE”, issued on 25 Mar. 2014, U.S. patentapplication Ser. No. 14/170,159, entitled “SUPPLEMENTING A HIGHPERFORMANCE ANALYTICS STORE WITH EVALUATION OF INDIVIDUAL EVENTS TORESPOND TO AN EVENT QUERY”, filed on 31 Jan. 2014, and U.S. patentapplication Ser. No. 14/815,973, entitled “STORAGE MEDIUM AND CONTROLDEVICE”, filed on 21 Feb. 2014, each of which is hereby incorporated byreference in its entirety.

2.10.4. Accelerating Report Generation

In some embodiments, a data server system such as the SPLUNK® ENTERPRISEsystem can accelerate the process of periodically generating updatedreports based on query results. To accelerate this process, asummarization engine automatically examines the query to determinewhether generation of updated reports can be accelerated by creatingintermediate summaries. If reports can be accelerated, the summarizationengine periodically generates a summary covering data obtained during alatest non-overlapping time period. For example, where the query seeksevents meeting a specified criteria, a summary for the time periodincludes only events within the time period that meet the specifiedcriteria. Similarly, if the query seeks statistics calculated from theevents, such as the number of events that match the specified criteria,then the summary for the time period includes the number of events inthe period that match the specified criteria.

In addition to the creation of the summaries, the summarization engineschedules the periodic updating of the report associated with the query.During each scheduled report update, the query engine determines whetherintermediate summaries have been generated covering portions of the timeperiod covered by the report update. If so, then the report is generatedbased on the information contained in the summaries. Also, if additionalevent data has been received and has not yet been summarized, and isrequired to generate the complete report, the query can be run on thisadditional event data. Then, the results returned by this query on theadditional event data, along with the partial results obtained from theintermediate summaries, can be combined to generate the updated report.This process is repeated each time the report is updated. Alternatively,if the system stores events in buckets covering specific time ranges,then the summaries can be generated on a bucket-by-bucket basis. Notethat producing intermediate summaries can save the work involved inre-running the query for previous time periods, so advantageously onlythe newer event data needs to be processed while generating an updatedreport. These report acceleration techniques are described in moredetail in U.S. Pat. No. 8,589,403, entitled “COMPRESSED JOURNALING INEVENT TRACKING FILES FOR METADATA RECOVERY AND REPLICATION”, issued on19 Nov. 2013, U.S. Pat. No. 8,412,696, entitled “REAL TIME SEARCHING ANDREPORTING”, issued on 2 Apr. 2011, and U.S. Pat. Nos. 8,589,375 and8,589,432, both also entitled “REAL TIME SEARCHING AND REPORTING”, bothissued on 19 Nov. 2013, each of which is hereby incorporated byreference in its entirety.

2.11. Security Features

The SPLUNK® ENTERPRISE platform provides various schemas, dashboards andvisualizations that simplify developers' task to create applicationswith additional capabilities. One such application is the SPLUNK® APPFOR ENTERPRISE SECURITY, which performs monitoring and alertingoperations and includes analytics to facilitate identifying both knownand unknown security threats based on large volumes of data stored bythe SPLUNK® ENTERPRISE system. SPLUNK® APP FOR ENTERPRISE SECURITYprovides the security practitioner with visibility intosecurity-relevant threats found in the enterprise infrastructure bycapturing, monitoring, and reporting on data from enterprise securitydevices, systems, and applications. Through the use of SPLUNK®ENTERPRISE searching and reporting capabilities, SPLUNK® APP FORENTERPRISE SECURITY provides a top-down and bottom-up view of anorganization's security posture.

The SPLUNK® APP FOR ENTERPRISE SECURITY leverages SPLUNK® ENTERPRISEsearch-time normalization techniques, saved searches, and correlationsearches to provide visibility into security-relevant threats andactivity and generate notable events for tracking. The App enables thesecurity practitioner to investigate and explore the data to find new orunknown threats that do not follow signature-based patterns.

Conventional Security Information and Event Management (SIEM) systemsthat lack the infrastructure to effectively store and analyze largevolumes of security-related data. Traditional SIEM systems typically usefixed schemas to extract data from pre-defined security-related fieldsat data ingestion time and storing the extracted data in a relationaldatabase. This traditional data extraction process (and associatedreduction in data size) that occurs at data ingestion time inevitablyhampers future incident investigations that may need original data todetermine the root cause of a security issue, or to detect the onset ofan impending security threat.

In contrast, the SPLUNK® APP FOR ENTERPRISE SECURITY system stores largevolumes of minimally processed security-related data at ingestion timefor later retrieval and analysis at search time when a live securitythreat is being investigated. To facilitate this data retrieval process,the SPLUNK® APP FOR ENTERPRISE SECURITY provides pre-specified schemasfor extracting relevant values from the different types ofsecurity-related event data and enables a user to define such schemas.

The SPLUNK® APP FOR ENTERPRISE SECURITY can process many types ofsecurity-related information. In general, this security-relatedinformation can include any information that can be used to identifysecurity threats. For example, the security-related information caninclude network-related information, such as IP addresses, domain names,asset identifiers, network traffic volume, uniform resource locatorstrings, and source addresses. The process of detecting security threatsfor network-related information is further described in U.S. Pat. No.8,826,434, entitled “SECURITY THREAT DETECTION BASED ON INDICATIONS INBIG DATA OF ACCESS TO NEWLY REGISTERED DOMAINS”, issued on 2 Sep. 2014,U.S. patent application Ser. No. 13/956,252, entitled “INVESTIGATIVE ANDDYNAMIC DETECTION OF POTENTIAL SECURITY-THREAT INDICATORS FROM EVENTS INBIG DATA”, filed on 31 Jul. 2013, U.S. patent application Ser. No.14/445,018, entitled “GRAPHIC DISPLAY OF SECURITY THREATS BASED ONINDICATIONS OF ACCESS TO NEWLY REGISTERED DOMAINS”, filed on 28 Jul.2014, U.S. patent application Ser. No. 14/445,023, entitled “SECURITYTHREAT DETECTION OF NEWLY REGISTERED DOMAINS”, filed on 28 Jul. 2014,U.S. patent application Ser. No. 14/815,971, entitled “SECURITY THREATDETECTION USING DOMAIN NAME ACCESSES”, filed on 1 Aug. 2015, and U.S.patent application Ser. No. 14/815,972, entitled “SECURITY THREATDETECTION USING DOMAIN NAME REGISTRATIONS”, filed on 1 Aug. 2015, eachof which is hereby incorporated by reference in its entirety for allpurposes. Security-related information can also include malwareinfection data and system configuration information, as well as accesscontrol information, such as login/logout information and access failurenotifications. The security-related information can originate fromvarious sources within a data center, such as hosts, virtual machines,storage devices and sensors. The security-related information can alsooriginate from various sources in a network, such as routers, switches,email servers, proxy servers, gateways, firewalls andintrusion-detection systems.

During operation, the SPLUNK® APP FOR ENTERPRISE SECURITY facilitatesdetecting “notable events” that are likely to indicate a securitythreat. These notable events can be detected in a number of ways: (1) auser can notice a correlation in the data and can manually identify acorresponding group of one or more events as “notable;” or (2) a usercan define a “correlation search” specifying criteria for a notableevent, and every time one or more events satisfy the criteria, theapplication can indicate that the one or more events are notable. A usercan alternatively select a pre-defined correlation search provided bythe application. Note that correlation searches can be run continuouslyor at regular intervals (e.g., every hour) to search for notable events.Upon detection, notable events can be stored in a dedicated “notableevents index,” which can be subsequently accessed to generate variousvisualizations containing security-related information. Also, alerts canbe generated to notify system operators when important notable eventsare discovered.

The SPLUNK® APP FOR ENTERPRISE SECURITY provides various visualizationsto aid in discovering security threats, such as a “key indicators view”that enables a user to view security metrics, such as counts ofdifferent types of notable events. For example, FIG. 9A illustrates anexample key indicators view 900 that comprises a dashboard, which candisplay a value 901, for various security-related metrics, such asmalware infections 902. It can also display a change in a metric value903, which indicates that the number of malware infections increased by63 during the preceding interval. Key indicators view 900 additionallydisplays a histogram panel 904 that displays a histogram of notableevents organized by urgency values, and a histogram of notable eventsorganized by time intervals. This key indicators view is described infurther detail in pending U.S. patent application Ser. No. 13/956,338,entitled “KEY INDICATORS VIEW”, filed on 31 Jul. 2013, and which ishereby incorporated by reference in its entirety for all purposes.

These visualizations can also include an “incident review dashboard”that enables a user to view and act on “notable events.” These notableevents can include: (1) a single event of high importance, such as anyactivity from a known web attacker; or (2) multiple events thatcollectively warrant review, such as a large number of authenticationfailures on a host followed by a successful authentication. For example,FIG. 9B illustrates an example incident review dashboard 910 thatincludes a set of incident attribute fields 911 that, for example,enables a user to specify a time range field 912 for the displayedevents. It also includes a timeline 913 that graphically illustrates thenumber of incidents that occurred in time intervals over the selectedtime range. It additionally displays an events list 914 that enables auser to view a list of all of the notable events that match the criteriain the incident attributes fields 911. To facilitate identifyingpatterns among the notable events, each notable event can be associatedwith an urgency value (e.g., low, medium, high, critical), which isindicated in the incident review dashboard. The urgency value for adetected event can be determined based on the severity of the event andthe priority of the system component associated with the event.

2.12. Data Center Monitoring

As mentioned above, the SPLUNK® ENTERPRISE platform provides variousfeatures that simplify the developer's task to create variousapplications. One such application is SPLUNK® APP FOR VMWARE® thatprovides operational visibility into granular performance metrics, logs,tasks and events, and topology from hosts, virtual machines and virtualcenters. It empowers administrators with an accurate real-time pictureof the health of the environment, proactively identifying performanceand capacity bottlenecks.

Conventional data-center-monitoring systems lack the infrastructure toeffectively store and analyze large volumes of machine-generated data,such as performance information and log data obtained from the datacenter. In conventional data-center-monitoring systems,machine-generated data is typically pre-processed prior to being stored,for example, by extracting pre-specified data items and storing them ina database to facilitate subsequent retrieval and analysis at searchtime. However, the rest of the data is not saved and discarded duringpre-processing.

In contrast, the SPLUNK® APP FOR VMWARE® stores large volumes ofminimally processed machine data, such as performance information andlog data, at ingestion time for later retrieval and analysis at searchtime when a live performance issue is being investigated. In addition todata obtained from various log files, this performance-relatedinformation can include values for performance metrics obtained throughan application programming interface (API) provided as part of thevSphere Hypervisor™ system distributed by VMware, Inc. of Palo Alto,California. For example, these performance metrics can include: (1)CPU-related performance metrics; (2) disk-related performance metrics;(3) memory-related performance metrics; (4) network-related performancemetrics; (5) energy-usage statistics; (6) data-traffic-relatedperformance metrics; (7) overall system availability performancemetrics; (8) cluster-related performance metrics; and (9) virtualmachine performance statistics. Such performance metrics are describedin U.S. patent application Ser. No. 14/167,316, entitled “CORRELATIONFOR USER-SELECTED TIME RANGES OF VALUES FOR PERFORMANCE METRICS OFCOMPONENTS IN AN INFORMATION-TECHNOLOGY ENVIRONMENT WITH LOG DATA FROMTHAT INFORMATION-TECHNOLOGY ENVIRONMENT”, filed on 29 Jan. 2014, andwhich is hereby incorporated by reference in its entirety for allpurposes.

To facilitate retrieving information of interest from performance dataand log files, the SPLUNK® APP FOR VMWARE® provides pre-specifiedschemas for extracting relevant values from different types ofperformance-related event data, and also enables a user to define suchschemas.

The SPLUNK® APP FOR VMWARE® additionally provides various visualizationsto facilitate detecting and diagnosing the root cause of performanceproblems. For example, one such visualization is a “proactive monitoringtree” that enables a user to easily view and understand relationshipsamong various factors that affect the performance of a hierarchicallystructured computing system. This proactive monitoring tree enables auser to easily navigate the hierarchy by selectively expanding nodesrepresenting various entities (e.g., virtual centers or computingclusters) to view performance information for lower-level nodesassociated with lower-level entities (e.g., virtual machines or hostsystems). Example node-expansion operations are illustrated in FIG. 9C,wherein nodes 933 and 934 are selectively expanded. Note that nodes931-939 can be displayed using different patterns or colors to representdifferent performance states, such as a critical state, a warning state,a normal state or an unknown/offline state. The ease of navigationprovided by selective expansion in combination with the associatedperformance-state information enables a user to quickly diagnose theroot cause of a performance problem. The proactive monitoring tree isdescribed in further detail in U.S. patent application Ser. No.14/253,490, entitled “PROACTIVE MONITORING TREE WITH SEVERITY STATESORTING”, filed on 15 Apr. 2014, and U.S. patent application Ser. No.14/812,948, also entitled “PROACTIVE MONITORING TREE WITH SEVERITY STATESORTING”, filed on 29 Jul. 2015, each of which is hereby incorporated byreference in its entirety for all purposes.

The SPLUNK® APP FOR VMWARE® also provides a user interface that enablesa user to select a specific time range and then view heterogeneous datacomprising events, log data, and associated performance metrics for theselected time range. For example, the screen illustrated in FIG. 9Ddisplays a listing of recent “tasks and events” and a listing of recent“log entries” for a selected time range above a performance-metric graphfor “average CPU core utilization” for the selected time range. Notethat a user is able to operate pull-down menus 942 to selectivelydisplay different performance metric graphs for the selected time range.This enables the user to correlate trends in the performance-metricgraph with corresponding event and log data to quickly determine theroot cause of a performance problem. This user interface is described inmore detail in U.S. patent application Ser. No. 14/167,316, entitled“CORRELATION FOR USER-SELECTED TIME RANGES OF VALUES FOR PERFORMANCEMETRICS OF COMPONENTS IN AN INFORMATION-TECHNOLOGY ENVIRONMENT WITH LOGDATA FROM THAT INFORMATION-TECHNOLOGY ENVIRONMENT”, filed on 29 Jan.2014, and which is hereby incorporated by reference in its entirety forall purposes.

2.13. Cloud-Based System Overview

The example data intake and query system 108 described in reference toFIG. 2 comprises several system components, including one or moreforwarders, indexers, and search heads. In some environments, a user ofa data intake and query system 108 may install and configure, oncomputing devices owned and operated by the user, one or more softwareapplications that implement some or all of these system components. Forexample, a user may install a software application on server computersowned by the user and configure each server to operate as one or more ofa forwarder, an indexer, a search head, etc. This arrangement generallymay be referred to as an “on-premises” solution. That is, the system 108is installed and operates on computing devices directly controlled bythe user of the system. Some users may prefer an on-premises solutionbecause it may provide a greater level of control over the configurationof certain aspects of the system (e.g., security, privacy, standards,controls, etc.). However, other users may instead prefer an arrangementin which the user is not directly responsible for providing and managingthe computing devices upon which various components of system 108operate.

In one embodiment, to provide an alternative to an entirely on-premisesenvironment for system 108, one or more of the components of a dataintake and query system instead may be provided as a cloud-basedservice. In this context, a cloud-based service refers to a servicehosted by one more computing resources that are accessible to end usersover a network, for example, by using a web browser or other applicationon a client device to interface with the remote computing resources. Forexample, a service provider may provide a cloud-based data intake andquery system by managing computing resources configured to implementvarious aspects of the system (e.g., forwarders, indexers, search heads,etc.) and by providing access to the system to end users via a network.Typically, a user may pay a subscription or other fee to use such aservice. Each subscribing user of the cloud-based service may beprovided with an account that enables the user to configure a customizedcloud-based system based on the user's preferences.

FIG. 10 illustrates a block diagram of an example cloud-based dataintake and query system. Similar to the system of FIG. 2 , the networkedcomputer system 1000 includes input data sources 202 and forwarders 204.These input data sources and forwarders may be in a subscriber's privatecomputing environment. Alternatively, they might be directly managed bythe service provider as part of the cloud service. In the example system1000, one or more forwarders 204 and client devices 1002 are coupled toa cloud-based data intake and query system 1006 via one or more networks1004. Network 1004 broadly represents one or more LANs, WANs, cellularnetworks, intranetworks, internetworks, etc., using any of wired,wireless, terrestrial microwave, satellite links, etc., and may includethe public Internet, and is used by client devices 1002 and forwarders204 to access the system 1006. Similar to the system of 108, each of theforwarders 204 may be configured to receive data from an input sourceand to forward the data to other components of the system 1006 forfurther processing.

In an embodiment, a cloud-based data intake and query system 1006 maycomprise a plurality of system instances 1008. In general, each systeminstance 1008 may include one or more computing resources managed by aprovider of the cloud-based system 1006 made available to a particularsubscriber. The computing resources comprising a system instance 1008may, for example, include one or more servers or other devicesconfigured to implement one or more forwarders, indexers, search heads,and other components of a data intake and query system, similar tosystem 108. As indicated above, a subscriber may use a web browser orother application of a client device 1002 to access a web portal orother interface that enables the subscriber to configure an instance1008.

Providing a data intake and query system as described in reference tosystem 108 as a cloud-based service presents a number of challenges.Each of the components of a system 108 (e.g., forwarders, indexers andsearch heads) may at times refer to various configuration files storedlocally at each component. These configuration files typically mayinvolve some level of user configuration to accommodate particular typesof data a user desires to analyze and to account for other userpreferences. However, in a cloud-based service context, users typicallymay not have direct access to the underlying computing resourcesimplementing the various system components (e.g., the computingresources comprising each system instance 1008) and may desire to makesuch configurations indirectly, for example, using one or more web-basedinterfaces. Thus, the techniques and systems described herein forproviding user interfaces that enable a user to configure source typedefinitions are applicable to both on-premises and cloud-based servicecontexts, or some combination thereof (e.g., a hybrid system where bothan on-premises environment such as SPLUNK® ENTERPRISE and a cloud-basedenvironment such as SPLUNK CLOUD™ are centrally visible).

2.14. Searching Externally Archived Data

FIG. 11 shows a block diagram of an example of a data intake and querysystem 108 that provides transparent search facilities for data systemsthat are external to the data intake and query system. Such facilitiesare available in the HUNK® system provided by Splunk Inc. of SanFrancisco, California. HUNK® represents an analytics platform thatenables business and IT teams to rapidly explore, analyze, and visualizedata in Hadoop and NoSQL data stores.

The search head 210 of the data intake and query system receives searchrequests from one or more client devices 1104 over network connections1120. As discussed above, the data intake and query system 108 mayreside in an enterprise location, in the cloud, etc. FIG. 11 illustratesthat multiple client devices 1104 a, 1104 b, . . . , 1104 n maycommunicate with the data intake and query system 108. The clientdevices 1104 may communicate with the data intake and query system usinga variety of connections. For example, one client device in FIG. 11 isillustrated as communicating over an Internet (Web) protocol, anotherclient device is illustrated as communicating via a command lineinterface, and another client device is illustrated as communicating viaa system developer kit (SDK).

The search head 210 analyzes the received search request to identifyrequest parameters. If a search request received from one of the clientdevices 1104 references an index maintained by the data intake and querysystem, then the search head 210 connects to one or more indexers 206 ofthe data intake and query system for the index referenced in the requestparameters. That is, if the request parameters of the search requestreference an index, then the search head accesses the data in the indexvia the indexer. The data intake and query system 108 may include one ormore indexers 206, depending on system access resources andrequirements. As described further below, the indexers 206 retrieve datafrom their respective local data stores 208 as specified in the searchrequest. The indexers and their respective data stores can comprise oneor more storage devices and typically reside on the same system, thoughthey may be connected via a local network connection.

If the request parameters of the received search request reference anexternal data collection, which is not accessible to the indexers 206 orunder the management of the data intake and query system, then thesearch head 210 can access the external data collection through anExternal Result Provider (ERP) process 1110. An external data collectionmay be referred to as a “virtual index” (plural, “virtual indices”). AnERP process provides an interface through which the search head 210 mayaccess virtual indices.

Thus, a search reference to an index of the system relates to a locallystored and managed data collection. In contrast, a search reference to avirtual index relates to an externally stored and managed datacollection, which the search head may access through one or more ERPprocesses 1110, 1112. FIG. 11 shows two ERP processes 1110, 1112 thatconnect to respective remote (external) virtual indices, which areindicated as a Hadoop or another system 1114 (e.g., Amazon S3, AmazonEMR, other Hadoop Compatible File Systems (HCFS), etc.) and a relationaldatabase management system (RDBMS) 1116. Other virtual indices mayinclude other file organizations and protocols, such as Structured QueryLanguage (SQL) and the like. The ellipses between the ERP processes1110, 1112 indicate optional additional ERP processes of the data intakeand query system 108. An ERP process may be a computer process that isinitiated or spawned by the search head 210 and is executed by thesearch data intake and query system 108. Alternatively or additionally,an ERP process may be a process spawned by the search head 210 on thesame or different host system as the search head 210 resides.

The search head 210 may spawn a single ERP process in response tomultiple virtual indices referenced in a search request, or the searchhead may spawn different ERP processes for different virtual indices.Generally, virtual indices that share common data configurations orprotocols may share ERP processes. For example, all search queryreferences to a Hadoop file system may be processed by the same ERPprocess, if the ERP process is suitably configured. Likewise, all searchquery references to an SQL database may be processed by the same ERPprocess. In addition, the search head may provide a common ERP processfor common external data source types (e.g., a common vendor may utilizea common ERP process, even if the vendor includes different data storagesystem types, such as Hadoop and SQL). Common indexing schemes also maybe handled by common ERP processes, such as flat text files or Weblogfiles.

The search head 210 determines the number of ERP processes to beinitiated via the use of configuration parameters that are included in asearch request message. Generally, there is a one-to-many relationshipbetween an external results provider “family” and ERP processes. Thereis also a one-to-many relationship between an ERP process andcorresponding virtual indices that are referred to in a search request.For example, using RDBMS, assume two independent instances of such asystem by one vendor, such as one RDBMS for production and another RDBMSused for development. In such a situation, it is likely preferable (butoptional) to use two ERP processes to maintain the independent operationas between production and development data. Both of the ERPs, however,will belong to the same family, because the two RDBMS system types arefrom the same vendor.

The ERP processes 1110, 1112 receive a search request from the searchhead 210. The search head may optimize the received search request forexecution at the respective external virtual index. Alternatively, theERP process may receive a search request as a result of analysisperformed by the search head or by a different system process. The ERPprocesses 1110, 1112 can communicate with the search head 210 viaconventional input/output routines (e.g., standard in/standard out,etc.). In this way, the ERP process receives the search request from aclient device such that the search request may be efficiently executedat the corresponding external virtual index.

The ERP processes 1110, 1112 may be implemented as a process of the dataintake and query system. Each ERP process may be provided by the dataintake and query system, or may be provided by process or applicationproviders who are independent of the data intake and query system. Eachrespective ERP process may include an interface application installed ata computer of the external result provider that ensures propercommunication between the search support system and the external resultprovider. The ERP processes 1110, 1112 generate appropriate searchrequests in the protocol and syntax of the respective virtual indices1114, 1116, each of which corresponds to the search request received bythe search head 210. Upon receiving search results from theircorresponding virtual indices, the respective ERP process passes theresult to the search head 210, which may return or display the resultsor a processed set of results based on the returned results to therespective client device.

Client devices 1104 may communicate with the data intake and querysystem 108 through a network interface 1120, e.g., one or more LANs,WANs, cellular networks, intranetworks, and/or internetworks using anyof wired, wireless, terrestrial microwave, satellite links, etc., andmay include the public Internet.

The analytics platform utilizing the External Result Provider processdescribed in more detail in U.S. Pat. No. 8,738,629, entitled “EXTERNALRESULT PROVIDED PROCESS FOR RETRIEVING DATA STORED USING A DIFFERENTCONFIGURATION OR PROTOCOL”, issued on 27 May 2014, U.S. Pat. No.8,738,587, entitled “PROCESSING A SYSTEM SEARCH REQUEST BY RETRIEVINGRESULTS FROM BOTH A NATIVE INDEX AND A VIRTUAL INDEX”, issued on 25 Jul.2013, U.S. patent application Ser. No. 14/266,832, entitled “PROCESSINGA SYSTEM SEARCH REQUEST ACROSS DISPARATE DATA COLLECTION SYSTEMS”, filedon 1 May 2014, and U.S. patent application Ser. No. 14/449,144, entitled“PROCESSING A SYSTEM SEARCH REQUEST INCLUDING EXTERNAL DATA SOURCES”,filed on 31 Jul. 2014, each of which is hereby incorporated by referencein its entirety for all purposes.

2.14.1. ERP Process Features

The ERP processes described above may include two operation modes: astreaming mode and a reporting mode. The ERP processes can operate instreaming mode only, in reporting mode only, or in both modessimultaneously. Operating in both modes simultaneously is referred to asmixed mode operation. In a mixed mode operation, the ERP at some pointcan stop providing the search head with streaming results and onlyprovide reporting results thereafter, or the search head at some pointmay start ignoring streaming results it has been using and only usereporting results thereafter.

The streaming mode returns search results in real time, with minimalprocessing, in response to the search request. The reporting modeprovides results of a search request with processing of the searchresults prior to providing them to the requesting search head, which inturn provides results to the requesting client device. ERP operationwith such multiple modes provides greater performance flexibility withregard to report time, search latency, and resource utilization.

In a mixed mode operation, both streaming mode and reporting mode areoperating simultaneously. The streaming mode results (e.g., the raw dataobtained from the external data source) are provided to the search head,which can then process the results data (e.g., break the raw data intoevents, timestamp it, filter it, etc.) and integrate the results datawith the results data from other external data sources, and/or from datastores of the search head. The search head performs such processing andcan immediately start returning interim (streaming mode) results to theuser at the requesting client device; simultaneously, the search head iswaiting for the ERP process to process the data it is retrieving fromthe external data source as a result of the concurrently executingreporting mode.

In some instances, the ERP process initially operates in a mixed mode,such that the streaming mode operates to enable the ERP quickly toreturn interim results (e.g., some of the raw or unprocessed datanecessary to respond to a search request) to the search head, enablingthe search head to process the interim results and begin providing tothe client or search requester interim results that are responsive tothe query. Meanwhile, in this mixed mode, the ERP also operatesconcurrently in reporting mode, processing portions of raw data in amanner responsive to the search query. Upon determining that it hasresults from the reporting mode available to return to the search head,the ERP may halt processing in the mixed mode at that time (or somelater time) by stopping the return of data in streaming mode to thesearch head and switching to reporting mode only. The ERP at this pointstarts sending interim results in reporting mode to the search head,which in turn may then present this processed data responsive to thesearch request to the client or search requester. Typically the searchhead switches from using results from the ERP's streaming mode ofoperation to results from the ERP's reporting mode of operation when thehigher bandwidth results from the reporting mode outstrip the amount ofdata processed by the search head in the]streaming mode of ERPoperation.

A reporting mode may have a higher bandwidth because the ERP does nothave to spend time transferring data to the search head for processingall the raw data. In addition, the ERP may optionally direct anotherprocessor to do the processing.

The streaming mode of operation does not need to be stopped to gain thehigher bandwidth benefits of a reporting mode; the search head couldsimply stop using the streaming mode results—and start using thereporting mode results—when the bandwidth of the reporting mode hascaught up with or exceeded the amount of bandwidth provided by thestreaming mode. Thus, a variety of triggers and ways to accomplish asearch head's switch from using streaming mode results to usingreporting mode results may be appreciated by one skilled in the art.

The reporting mode can involve the ERP process (or an external system)performing event breaking, time stamping, filtering of events to matchthe search query request, and calculating statistics on the results. Theuser can request particular types of data, such as if the search queryitself involves types of events, or the search request may ask forstatistics on data, such as on events that meet the search request. Ineither case, the search head understands the query language used in thereceived query request, which may be a proprietary language. Oneexemplary query language is Splunk Processing Language (SPL) developedby the assignee of the application, Splunk Inc. The search headtypically understands how to use that language to obtain data from theindexers, which store data in a format used by the SPLUNK® Enterprisesystem.

The ERP processes support the search head, as the search head is notordinarily configured to understand the format in which data is storedin external data sources such as Hadoop or SQL data systems. Rather, theERP process performs that translation from the query submitted in thesearch support system's native format (e.g., SPL if SPLUNK® ENTERPRISEis used as the search support system) to a search query request formatthat will be accepted by the corresponding external data system. Theexternal data system typically stores data in a different format fromthat of the search support system's native index format, and it utilizesa different query language (e.g., SQL or MapReduce, rather than SPL orthe like).

As noted, the ERP process can operate in the streaming mode alone. Afterthe ERP process has performed the translation of the query request andreceived raw results from the streaming mode, the search head canintegrate the returned data with any data obtained from local datasources (e.g., native to the search support system), other external datasources, and other ERP processes (if such operations were required tosatisfy the terms of the search query). An advantage of mixed modeoperation is that, in addition to streaming mode, the ERP process isalso executing concurrently in reporting mode. Thus, the ERP process(rather than the search head) is processing query results (e.g.,performing event breaking, timestamping, filtering, possibly calculatingstatistics if required to be responsive to the search query request,etc.). It should be apparent to those skilled in the art that additionaltime is needed for the ERP process to perform the processing in such aconfiguration. Therefore, the streaming mode will allow the search headto start returning interim results to the user at the client devicebefore the ERP process can complete sufficient processing to startreturning any search results. The switchover between streaming andreporting mode happens when the ERP process determines that theswitchover is appropriate, such as when the ERP process determines itcan begin returning meaningful results from its reporting mode.

The operation described above illustrates the source of operationallatency: streaming mode has low latency (immediate results) and usuallyhas relatively low bandwidth (fewer results can be returned per unit oftime). In contrast, the concurrently running reporting mode hasrelatively high latency (it has to perform a lot more processing beforereturning any results) and usually has relatively high bandwidth (moreresults can be processed per unit of time). For example, when the ERPprocess does begin returning report results, it returns more processedresults than in the streaming mode, because, e.g., statistics only needto be calculated to be responsive to the search request. That is, theERP process doesn't have to take time to first return raw data to thesearch head. As noted, the ERP process could be configured to operate instreaming mode alone and return just the raw data for the search head toprocess in a way that is responsive to the search request.Alternatively, the ERP process can be configured to operate in thereporting mode only. Also, the ERP process can be configured to operatein streaming mode and reporting mode concurrently, as described, withthe ERP process stopping the transmission of streaming results to thesearch head when the concurrently running reporting mode has caught upand started providing results. The reporting mode does not require theprocessing of all raw data that is responsive to the search queryrequest before the ERP process starts returning results; rather, thereporting mode usually performs processing of chunks of events andreturns the processing results to the search head for each chunk.

For example, an ERP process can be configured to merely return thecontents of a search result file verbatim, with little or no processingof results. That way, the search head performs all processing (such asparsing byte streams into events, filtering, etc.). The ERP process canbe configured to perform additional intelligence, such as analyzing thesearch request and handling all the computation that a native searchindexer process would otherwise perform. In this way, the configured ERPprocess provides greater flexibility in features while operatingaccording to desired preferences, such as response latency and resourcerequirements.

2.14. IT Service Monitoring

As previously mentioned, the SPLUNK® ENTERPRISE platform providesvarious schemas, dashboards and visualizations that make it easy fordevelopers to create applications to provide additional capabilities.One such application is SPLUNK® IT SERVICE INTELLIGENCE™, which performsmonitoring and alerting operations. It also includes analytics to helpan analyst diagnose the root cause of performance problems based onlarge volumes of data stored by the SPLUNK® ENTERPRISE system ascorrelated to the various services an IT organization provides (aservice-centric view). This differs significantly from conventional ITmonitoring systems that lack the infrastructure to effectively store andanalyze large volumes of service-related event data. Traditional servicemonitoring systems typically use fixed schemas to extract data frompre-defined fields at data ingestion time, wherein the extracted data istypically stored in a relational database. This data extraction processand associated reduction in data content that occurs at data ingestiontime inevitably hampers future investigations, when all of the originaldata may be needed to determine the root cause of or contributingfactors to a service issue.

In contrast, a SPLUNK® IT SERVICE INTELLIGENCE™ system stores largevolumes of minimally-processed service-related data at ingestion timefor later retrieval and analysis at search time, to perform regularmonitoring, or to investigate a service issue. To facilitate this dataretrieval process, SPLUNK® IT SERVICE INTELLIGENCE™ enables a user todefine an IT operations infrastructure from the perspective of theservices it provides. In this service-centric approach, a service suchas corporate e-mail may be defined in terms of the entities employed toprovide the service, such as host machines and network devices. Eachentity is defined to include information for identifying all of theevent data that pertains to the entity, whether produced by the entityitself or by another machine, and considering the many various ways theentity may be identified in raw machine data (such as by a URL, an IPaddress, or machine name). The service and entity definitions canorganize event data around a service so that all of the event datapertaining to that service can be easily identified. This capabilityprovides a foundation for the implementation of Key PerformanceIndicators.

One or more Key Performance Indicators (KPI's) are defined for a servicewithin the SPLUNK® IT SERVICE INTELLIGENCE™ application. Each KPImeasures an aspect of service performance at a point in time or over aperiod of time (aspect KPI's). Each KPI is defined by a search querythat derives a KPI value from the machine data of events associated withthe entities that provide the service. Information in the entitydefinitions may be used to identify the appropriate events at the time aKPI is defined or whenever a KPI value is being determined. The KPIvalues derived over time may be stored to build a valuable repository ofcurrent and historical performance information for the service, and therepository, itself, may be subject to search query processing. AggregateKPIs may be defined to provide a measure of service performancecalculated from a set of service aspect KPI values; this aggregate mayeven be taken across defined timeframes and/or across multiple services.A particular service may have an aggregate KPI derived fromsubstantially all of the aspect KPI's of the service to indicate anoverall health score for the service.

SPLUNK® IT SERVICE INTELLIGENCE™ facilitates the production ofmeaningful aggregate KPI's through a system of KPI thresholds and statevalues. Different KPI definitions may produce values in differentranges, and so the same value may mean something very different from oneKPI definition to another. To address this, SPLUNK® IT SERVICEINTELLIGENCE™ implements a translation of individual KPI values to acommon domain of “state” values. For example, a KPI range of values maybe 1-100, or 50-275, while values in the state domain may be ‘critical,’‘warning,’ ‘normal,’ and ‘informational’. Thresholds associated with aparticular KPI definition determine ranges of values for that KPI thatcorrespond to the various state values. In one case, KPI values 95-100may be set to correspond to ‘critical’ in the state domain. KPI valuesfrom disparate KPI's can be processed uniformly once they are translatedinto the common state values using the thresholds. For example, “normal80% of the time” can be applied across various KPI's. To providemeaningful aggregate KPI's, a weighting value can be assigned to eachKPI so that its influence on the calculated aggregate KPI value isincreased or decreased relative to the other KPI's.

One service in an IT environment often impacts, or is impacted by,another service. SPLUNK® IT SERVICE INTELLIGENCE™ can reflect thesedependencies. For example, a dependency relationship between a corporatee-mail service and a centralized authentication service can be reflectedby recording an association between their respective servicedefinitions. The recorded associations establish a service dependencytopology that informs the data or selection options presented in a GUI,for example. (The service dependency topology is like a “map” showinghow services are connected based on their dependencies.) The servicetopology may itself be depicted in a GUI and may be interactive to allownavigation among related services.

Entity definitions in SPLUNK® IT SERVICE INTELLIGENCE™ can includeinformational fields that can serve as metadata, implied data fields, orattributed data fields for the events identified by other aspects of theentity definition. Entity definitions in SPLUNK® IT SERVICEINTELLIGENCE™ can also be created and updated by an import of tabulardata (as represented in a CSV, another delimited file, or a search queryresult set). The import may be GUI-mediated or processed using importparameters from a GUI-based import definition process. Entitydefinitions in SPLUNK® IT SERVICE INTELLIGENCE™ can also be associatedwith a service by means of a service definition rule. Processing therule results in the matching entity definitions being associated withthe service definition. The rule can be processed at creation time, andthereafter on a scheduled or on-demand basis. This allows dynamic,rule-based updates to the service definition.

During operation, SPLUNK® IT SERVICE INTELLIGENCE™ can recognizeso-called “notable events” that may indicate a service performanceproblem or other situation of interest. These notable events can berecognized by a “correlation search” specifying trigger criteria for anotable event: every time KPI values satisfy the criteria, theapplication indicates a notable event. A severity level for the notableevent may also be specified. Furthermore, when trigger criteria aresatisfied, the correlation search may additionally or alternativelycause a service ticket to be created in an IT service management (ITSM)system, such as a systems available from ServiceNow, Inc., of SantaClara, California.

SPLUNK® IT SERVICE INTELLIGENCE™ provides various visualizations builton its service-centric organization of event data and the KPI valuesgenerated and collected. Visualizations can be particularly useful formonitoring or investigating service performance. SPLUNK® IT SERVICEINTELLIGENCE™ provides a service monitoring interface suitable as thehome page for ongoing IT service monitoring. The interface isappropriate for settings such as desktop use or for a wall-mounteddisplay in a network operations center (NOC). The interface mayprominently display a services health section with tiles for theaggregate KPI's indicating overall health for defined services and ageneral KPI section with tiles for KPI's related to individual serviceaspects. These tiles may display KPI information in a variety of ways,such as by being colored and ordered according to factors like the KPIstate value. They also can be interactive and navigate to visualizationsof more detailed KPI information.

SPLUNK® IT SERVICE INTELLIGENCE™ provides a service-monitoring dashboardvisualization based on a user-defined template. The template can includeuser-selectable widgets of varying types and styles to display KPIinformation. The content and the appearance of widgets can responddynamically to changing KPI information. The KPI widgets can appear inconjunction with a background image, user drawing objects, or othervisual elements, that depict the IT operations environment, for example.The KPI widgets or other GUI elements can be interactive so as toprovide navigation to visualizations of more detailed KPI information.

SPLUNK® IT SERVICE INTELLIGENCE™ provides a visualization showingdetailed time-series information for multiple KPI's in parallel graphlanes. The length of each lane can correspond to a uniform time range,while the width of each lane may be automatically adjusted to fit thedisplayed KPI data. Data within each lane may be displayed in a userselectable style, such as a line, area, or bar chart. During operation auser may select a position in the time range of the graph lanes toactivate lane inspection at that point in time. Lane inspection maydisplay an indicator for the selected time across the graph lanes anddisplay the KPI value associated with that point in time for each of thegraph lanes. The visualization may also provide navigation to aninterface for defining a correlation search, using information from thevisualization to pre-populate the definition.

SPLUNK® IT SERVICE INTELLIGENCE™ provides a visualization for incidentreview showing detailed information for notable events. The incidentreview visualization may also show summary information for the notableevents over a time frame, such as an indication of the number of notableevents at each of a number of severity levels. The severity leveldisplay may be presented as a rainbow chart with the warmest colorassociated with the highest severity classification. The incident reviewvisualization may also show summary information for the notable eventsover a time frame, such as the number of notable events occurring withinsegments of the time frame. The incident review visualization maydisplay a list of notable events within the time frame ordered by anynumber of factors, such as time or severity. The selection of aparticular notable event from the list may display detailed informationabout that notable event, including an identification of the correlationsearch that generated the notable event.

SPLUNK® IT SERVICE INTELLIGENCE™ provides pre-specified schemas forextracting relevant values from the different types of service-relatedevent data. It also enables a user to define such schemas.

2.15 Cloud-Based Architecture

As shown in the previous figures, various embodiments may refer to adata intake and query system 108 that includes one or more of a searchhead 210, an indexer 206, and a forwarder 204. In other implementations,data intake and query system 108 may have a different architecture, butmay carry out indexing and searching in a way that is indistinguishableor functionally equivalent from the perspective of the end user. Forexample, data intake and query system 108 may be re-architected to runin a stateless, containerized environment. In some of these embodiments,data intake and query system 108 may be run in a computing cloudprovided by a third party, or provided by the operator of the dataintake and query system 108. This type of cloud-based data intake andquery system may have several benefits, including, but not limited to,lossless data ingestion, more robust disaster recovery, and faster ormore efficient processing, searching, and indexing. A cloud-based dataintake and query system as described in this section may provideseparately scalable storage resources and compute resources, orseparately scalable search and index resources. Additionally, thecloud-based data intake and query system may allow for applications tobe developed on top of the data intake and query system, to extend orenhance functionality, through a gateway layer or one or moreApplication Programming Interfaces (APIs), which may providecustomizable access control or targeted exposure to the workings of dataintake and query system 108.

In some embodiments, a cloud-based data intake and query system mayinclude an intake system. Such an intake system can include, but is notlimited to an intake buffer, such as Apache Kafka® or Amazon Kinesis®,or an extensible compute layer, such as Apache Spark™ or Apache Flink®.In some embodiments, the search function and the index function may beseparated or containerized, so that search functions and index functionsmay run or scale independently. In some embodiments, data that isindexed may be stored in buckets, which may be stored in a persistentstorage once certain bucket requirements have been met, and retrieved asneeded for searching. In some embodiments, the search functions andindex functions run in stateless containers, which may be coordinated byan orchestration platform. These containerized search and indexfunctions may retrieve data needed to carry out searching and indexingfrom the buckets or various other services that may also run incontainers, or within other components of the orchestration platform. Inthis manner, loss of a single container, or even multiple containers,does not result in data loss, because the data can be quickly recoveredfrom the various services or components or the buckets in which the datais persisted.

In some embodiments, the cloud-based data intake and query system mayimplement tenant-based and user-based access control. In someembodiments, the cloud-based data intake and query system may implementan abstraction layer, through a gateway portal, an API, or somecombination thereof, to control or limit access to the functionality ofthe cloud-based data intake and query system.

3.0 Overview of Facilitating Extraction Rule Enhancement and Validationin a Data Processing Environment

Utilizing appropriate extraction rules is important to perform dataextractions. Oftentimes, however, it is difficult to generate extractionrules that effectively extract desired data. For example, in some cases,there is a limited amount of sample data sets (e.g., events) accessibleto use to generate extraction rules. As another example, varying dataformats can make it difficult to capture extraction rules applicable tothe various data formats. For example, even data associated with a samesourcetype may have varying data formats (e.g., different versions ofvendor product, customized formats, etc.). Irrespective of sample dataset size and data format variability, creating extraction rules througha user interface can be time consuming and challenging. Further, incases in which extraction rules are not properly functioning, userstypically are unsure as to how to fix the extraction rule.

Accordingly, embodiments of the present disclosure are directed tofacilitating extraction rule enhancement and validation. In particular,extraction rules can be analyzed to enhance and/or validate extractionrules. In some embodiments described herein, a set of extraction rulesfor use in extracting data can be enhanced by utilizing user feedbackpertaining to extraction rules to supplement or customize the extractionrules for subsequent use. In other embodiments described herein, anextraction rule(s) for use in extraction data can be monitored toidentify whether the extraction rule is invalid. In cases that theextraction rule is deemed invalid, a new extraction rule may begenerated and, thereafter, applied to extract data. Further, the newlygenerated extraction rule can be used to supplement or customize theextraction rules for subsequent use.

3.1 Overview of a Field Extraction System in a Data ProcessingEnvironment

FIG. 18 illustrates an example data-processing environment 1800 inaccordance with various embodiments of the present disclosure.Generally, the data-processing environment 1800 refers to an environmentthat provides for, or enables, the management, storage, retrieval,preprocessing, processing, and/or analysis of data. As shown in FIG. 18, the distributed data processing environment includes a fieldextraction system 1816 used to facilitate enhancement and validation ofextraction rules.

In some embodiments, the environment 1800 can include a data-processingsystem 1802 communicatively coupled to one or more client devices 1804and one or more data sources 1806 via a communications network 1808. Thenetwork 1808 may include an element or system that facilitatescommunication between the entities of the environment 1800. The network1808 may include an electronic communications network, such as theInternet, a local area network (LAN), a wide area network (WAN), awireless local area network (WLAN), a cellular communications network,and/or the like. In some embodiments, the network 1808 can include awired or a wireless network. In some embodiments, the network 1808 caninclude a single network or a combination of networks.

The data source 1806 may be a source of incoming source data being fedinto the data-processing system 1802. A data source 1806 can be orinclude one or more external data sources, such as web servers,application servers, databases, firewalls, routers, operating systems,and software applications that execute on computer systems, mobiledevices, sensors, and/or the like. Data source 1806 may be locatedremote from the data-processing system 1802. For example, a data source1806 may be defined on an agent computer operating remote from thedata-processing system 1802, such as on-site at a customer's location,that transmits source data to data-processing system 1802 via acommunications network (e.g., network 1808).

Source data can be a stream or set of data fed to an entity of thedata-processing system 1802, such as a forwarder (not shown) or anindexer. In some embodiments, the source data can be heterogeneousmachine-generated data received from various data sources 1806, such asservers, databases, applications, networks, and/or the like. Source datamay include, for example raw data, such as server log files, activitylog files, configuration files, messages, network packet data,performance measurements, sensor measurements, and/or the like. Forexample, source data may include log data generated by a server duringthe normal course of operation (e.g. server log data).

As can be appreciated, source data might be structured data orunstructured data. Structured data has a predefined format, whereinspecific data items with specific data formats reside at predefinedlocations in the data. For example, data contained in relationaldatabases and spreadsheets may be structured data sets. In contrast,unstructured data does not have a predefined format. This means thatunstructured data can comprise various data items having different datatypes that can reside at different locations.

The indexer 1812 of the data-processing system 1802 receives the sourcedata, for example, from a forwarder (not shown) or the data source 1806,and can apportion the source data into events. An indexer 1812 may be anentity of the data-processing system 1802 that indexes data,transforming source data into events and placing the results into a datastore 1814, or index. An indexer 1812 may perform other functions, suchas data input and search management. In some cases, forwarders (notshown) handle data input, and forward the source data to the indexers1812 for indexing.

During indexing, and at a high-level, the indexer 1812 can facilitatetaking data from its origin in sources, such as log files and networkfeeds, to its transformation into searchable events that encapsulatevaluable knowledge. The indexer 1812 may acquire a raw data stream(e.g., source data) from its source (e.g., data source 1806), break itinto blocks (e.g., 64K blocks of data), and/or annotate each block withmetadata keys. After the data has been input, the data can be parsed.This can include, for example, identifying event boundaries, identifyingevent timestamps (or creating them if they don't exist), applying custommetadata to incoming events, and/or the like. Accordingly, the raw datamay be data broken into individual events. As discussed, an eventgenerally refers to a portion, or a segment of the data, that isassociated with a time (e.g., via a timestamp). And, the resultingevents may be indexed (e.g., stored in a raw data file associated withan index file). In some embodiments, indexing the source data mayinclude additional processing, such as compression, replication, and/orthe like.

The data store 1814 may include a medium for the storage of datathereon. For example, data store 1814 may include non-transitorycomputer-readable medium storing data thereon that is accessible byentities of the environment 1800, such as the corresponding indexer 1812and the field extraction system 1816. As can be appreciated, the datastore 1814 may store the data (e.g., events) in any manner In someimplementations, the data may include one or more indexes including oneor more buckets, and the buckets may include an index file and/or rawdata file (e.g., including parsed, time-stamped events). In someembodiments, each data store is managed by a given indexer that storesdata to the data store and/or performs searches of the data stored onthe data store. Although certain embodiments are described with regardto a single data store 1814 for purposes of illustration, embodimentsmay include employing multiple data stores 1814, such as a plurality ofdistributed data stores 1814.

As described, events within the data store 1814 may be represented by adata structure that is associated with a certain point in time andincludes a portion of raw machine data (e.g., a portion ofmachine-generated data that has not been manipulated). An event mayinclude, for example, a line of data that includes a time reference(e.g., a timestamp), and one or more other values. In the context ofserver log data, for example, an event may correspond to a log entry fora client request and include the following values: (a) a time value(e.g., including a value for the date and time of the request, such as atimestamp), and (b) a series of other values including, for example, apage value (e.g., including a value representing the page requested), anIP (Internet Protocol) value (e.g., including a value for representingthe client IP address associated with the request), and an HTTP(Hypertext Transfer protocol) code value (e.g., including a valuerepresentative of an HTTP status code), and/or the like. That is, eachevent may be associated with one or more values. Some events may beassociated with default values, such as a host value, a source value, asource type value and/or a time value. A default value may be common tosome or all events of a set of source data.

In some embodiments, an event can be associated with one or morecharacteristics that are not represented by the data initially containedin the raw data, such as characteristics of the host, the source, and/orthe source type associated with the event. In the context of server logdata, for example, if an event corresponds to a log entry received fromServer A, the host and the source of the event may be identified asServer A, and the source type may be determined to be “server.” In someembodiments, values representative of the characteristics may be addedto (or otherwise associated with) the event. In the context of serverlog data, for example, if an event is received from Server A, a hostvalue (e.g., including a value representative of Server A), a sourcevalue (e.g., including a value representative of Server A), and a sourcetype value (e.g., including a value representative of a “server”) may beappended to (or otherwise associated with) the corresponding event.

In some embodiments, events can correspond to data that is generated ona regular basis and/or in response to the occurrence of a givenactivity. In the context of server log data, for example, a server thatlogs activity every second may generate a log entry every second, andthe log entries may be stored as corresponding events of the sourcedata. Similarly, a server that logs data upon the occurrence of an errormay generate a log entry each time an error occurs, and the log entriesmay be stored as corresponding events of the source data.

Upon obtaining events, the field extraction system 1816 can facilitatethe enhancement and/or validation of extraction rules relevant to theevents, or portion thereof. Although the field extraction system 1816 isillustrated and described herein as a separate component, this is forillustrative purposes. As can be appreciated, the field extractionsystem 1816, or functions described in association therewith, can beperformed at the indexer 1812, a search head, and/or any other componentassociated with or in communication with a data-processing system. Forexample, some functionality described in association with thedata-processing system 1816 might be performed at a search head, whileother functionality described in association with the data-processingsystem 1816 might be performed at an indexer. Further, the fieldextraction system 1816, or a portion thereof, may function in acloud-based environment (e.g., a cloud-based data intake and querysystem).

As described herein, the field extraction system 1816, or portionthereof, can be initiated by a user of the client device 1804. Theclient device 1804 may be used or otherwise accessed by a user, such asa system administrator or a customer. A client device 1804 may includeany variety of electronic devices. In some embodiments, a client device1804 can include a device capable of communicating information via thenetwork 1808. A client device 1804 may include one or more computerdevices, such as a desktop computer, a server, a laptop computer, atablet computer, a wearable computer device, a personal digitalassistant (PDA), a smart phone, and/or the like. In some embodiments, aclient device 1804 may be a client of the data-processing system 1802.In some embodiments, a client device 1804 can include variousinput/output (I/O) interfaces, such as a display (e.g., for displaying agraphical user interface (GUI), an audible output user interface (e.g.,a speaker), an audible input user interface (e.g., a microphone), animage acquisition interface (e.g., a camera), a keyboard, apointer/selection device (e.g., a mouse, a trackball, a touchpad, atouchscreen, a gesture capture or detecting device, or a stylus), and/orthe like. In some embodiments, a client device 1804 can include generalcomputing components and/or embedded systems optimized with specificcomponents for performing specific tasks. In some embodiments, a clientdevice 1804 can include programs/applications that can be used togenerate a request for content, to provide content, to render content,and/or to send and/or receive requests to and/or from other devices viathe network 1808. For example, a client device 1804 may include anInternet browser application that facilitates communication with thedata-processing system 1802 via the network 1808. In some embodiments, aprogram, or application, of a client device 1804 can include programmodules having program instructions that are executable by a computersystem to perform some or all of the functionality described herein withregard to at least client device 1804. In some embodiments, a clientdevice 1804 can include one or more computer systems similar to that ofthe computer system 2400 described below with regard to at least FIG. 24.

Enhancement and/or validation of extraction rules can be initiated ortriggered at the client device 1804 via a graphical user interface(GUI). In some embodiments, the data-processing system 1802 can providefor the display of a GUI. Such a GUI can be displayed on a client device1804, and can present information relating to initiating extraction ruleidentification, extraction rule enhancement, extraction rule analysis,or extraction rule validation; performing data extraction; and/orviewing results or alerts associated with extraction rule analysis ordata extraction.

Performing extraction rule analysis to enhance and/or validateextraction rules can be initiated in any number of ways. In oneimplementation, extraction rule analysis can be initiated at a clientdevice (e.g., by a user). As one example, a user may initiate extractionrule analysis prior to or in accordance with performing a search forinformation. For instance, an extraction rule analysis may beautomatically triggered in accordance with a search being initiated inassociation with a query input by a user. As another example, a user mayselect an icon or other indicator to specifically initiate an extractionrule analysis (e.g., in association with or separate from performing asearch). For example, assume a user desires to perform field extractionor enhance extraction rules. In such a case, a user may select to uploaddata, or events, for use in enhancing and/or validating extraction rulesin association with such events.

In addition or in the alternative to performing extraction rule analysisat search time (e.g., upon the events being created, indexed, andstored), extraction rule analysis can be applied before or as events arecreated, indexed, and/or stored (e.g., ingest time or index time).Accordingly, extraction rule analysis as described in association withthe field extraction system 1816 can additionally or alternatively beautomatically performed in association with indexing or as new data isreceived. In this way, as data is received and/or indexed, extractionrules may be enhanced and/or validated.

The field extraction system 1816 is generally configured to facilitateenhancement and/or validation of extraction rules. In particular, thefield extraction system 1816 performs extraction rule analysis toenhance and/or validate extraction rules. As described herein, anextraction rule can be applied to event data to extract values forspecific fields (e.g., during indexing, search time, etc.). Morespecifically, an extraction rule can include one or more instructionsthat specify how to extract a value for the field from the event data.An extraction rule can generally include any type of instruction forextracting values from data in events. In some cases, an extraction rulecomprises a regular expression where a sequence of characters form asearch pattern, in which case the rule is referred to as a “regex rule.”The system applies the regex rule to the event data to extract valuesfor associated fields in the event data by searching the event data forthe sequence of characters defined in the regex rule. As anotherexample, an extraction rule may utilize delimiters, headers, patterns,or the like to provide instruction for extraction values from data inevents.

As described, extraction rule analysis can be initiated or triggered inresponse to a query, user selection, and/or automatically. In thisregard, a user may input or select (e.g., via client device 1804) aquery to initiate extraction rule analysis. A query may be in any form,such as a search processing language (SPL) or a natural language form. Aquery may be provided to, for example, retrieve events that meetcriteria specified in a query, such as containing certain keywords orhaving specific values in defined fields. The query can trigger thefield extraction system 1816 to enhance and/or validate extractionrules. As another example, as a user inputs or uploads events, or asevents are automatically ingested or indexed, extraction rule analysismay be automatically initiated.

To perform extraction rule analysis, the field extraction system 1816may include a data processing component 1830, a rule matching component1832, a rule generating component 1834, a rule enhancing component 1836,and a rule validating component 1838. According to embodiments of theinvention, the field extraction system 1816 can include any number ofother components not illustrated. In some embodiments, one or more ofthe illustrated components 1830, 1832, 1834, 1836, and 1838 can beintegrated into a single component or can be divided into a number ofdifferent components. Components 1830-1838 can be implemented on anynumber of machines and can be integrated, as desired, with any number ofother functionalities or services. By way of example only, any number ofcomponents of a field extraction system 1816 may operate in acloud-based service.

The data-processing component 1830 is generally configured to performdata processing in association with a set of events, or event set. Inone embodiment, the data processing component 1830 is configured toanonymize sensitive or private data within the events. Sensitive orprivate data to be anonymized may include, for example, IP addresses,URLs, hosts, etc. By way of example only, IP addresses within events maybe identified and replaced with a default value (e.g., IPv4). In somecases, such data anonymization may occur automatically. For example,using a set of predefined anonymization rules, sensitive data may beremoved or replaced within events. In other cases, data anonymizationmay be triggered or initiated by a user. For example, upon providingevent data, a list or set of anonymization rules may be provided to auser via a graphical user interface (e.g., via client device 1804). Theuser may view the anonymization rules and select one or moreanonymization rules desired to be applied to anonymize or removesensitive data. Advantageously, as various implementations of thissystem enable multiple tenants or clients to utilize and benefit fromenhanced extraction rules, anonymization enables one tenant to leverageextraction rule feedback provided by another tenant.

As can be appreciated, such data anonymization may occur separate fromthe field extraction system 1816, or may not occur at all. Further, thedata processing component 1830 may additionally or alternatively provideother types of data processing services.

The rule matching component 1832 is configured to match a set of one ormore extraction rules with events. In this regard, the rule matchingcomponent 1834 can identify extraction rules that match or correspondwith events. Generally, an event matches or corresponds with anextraction rule when data (e.g., raw data) within an event includes apattern the extraction rule uses to extract a value for a field. By wayof example only, assume an extraction rule includes a pattern ofN.N.NN.NNN for an IP address, where N is a number. In cases that anevent includes 1.2.34.567, the extraction rule is determined to matchthe event. In cases that that the “N.N.NN.NNN” pattern does not existwithin an event, the extraction rule does not match or correspond withthe event.

Extraction rules may be stored in extraction rule data store 1842. Assuch, the rule matching component 1832 may reference extraction rulesstored in extraction rule data store 1842 and analyze such extractionrules to identify one or more extraction rules that correspond with ormatch an event set.

In some cases, the rule matching component 1832 may match events with arule package. A rule package generally refers to a particular set ofextraction rules. Generally, the extraction rules included in a rulepackage are related to one another in some manner. For example, a rulepackage can include a set of extraction rules associated with aparticular sourcetype. In this regard, a first rule package maycorrespond with a first source type, and a second rule package maycorrespond with a second source type. Each rule package may have variousextraction rules, for example, due to different log formats or vendorversions.

Rule packages can be stored in an extraction rule data store, forexample, within extraction rule data store 1842. Accordingly, the rulematching component 1832 can access rule packages within an extractionrule data store and analyze the extraction rules to identify a rulepackage having extraction rules that correspond with the particularevents.

Identifying a set of one or more extraction rules (e.g., a rule package)that match or correspond with a set of events can occur in any number ofways. In one implementation, the rule matching component 1832 maydetermine match rates associated with one or more extraction rules orrule packages. A match rate indicates an extent, proportion, percentage,or rate at which an extraction rule(s) (e.g., rule package) correspondswith events. In particular, for instance, a match rate for a rulepackage can indicate an extent, proportion, percentage, or rate at whichat least one extraction rule of a rule package corresponds with ormatches with events. By way of example only, an 88% match rateassociated with a first rule package indicates that at least oneextraction rule in a first rule package matches or corresponds with 88%of events within a set of events. Typically, an event will match onlyone extraction rule in a particular rule set, but that is not always thecase. As can be appreciated, in some cases, a match rate may bedetermined in association with each extraction rule, each rule package,or portions thereof. Accordingly, each extraction rule or rule packagemay be analyzed in light of a set of events to determine a match ratefor the corresponding rule or rule package.

The determined match rates can then be used to determine one or moreextraction rules that match an event set. For example, rule packagesassociated with a match rate above a threshold value (e.g., 30%, 50%,80%, etc.) may be considered a match with an event set. As anotherexample, rule packages associated with a predetermined number (e.g., 1,3, etc.) of highest match rates may be deemed a match with an event set.As yet another example, a maximum number of rule packages (e.g., 3)associated with the highest match rates and exceeding a threshold valuemay be deemed a match with an event set.

Advantageously, the match rates associated with rule packages can beused to infer sourcetype associated with the events. In this regard, incases that a rule package corresponds with a particular sourcetype, whena set of events are determined to match a particular rule package, itcan be inferred that the events are associated with the correspondingsourcetype. As described, a source type generally refers to a type ofsource associated with a data set (e.g., source from which the data isobtained or at which the data is collected). For instance, a first dataset may be provided via a first source type of a router, while a seconddata set may be provided via a second source type of a mobile device.Example source types include access_combined, cisco_syslog,apache_error, websphere_core, Linux, other log formats, etc.

Inferring a sourcetype can be valuable for any number of reasons, suchas, for example, enabling verification of utilization of a correct rulepackage, tagging the event(s) as the sourcetype (e.g., when an eventdoes not already have a corresponding sourcetype), etc. The “sourcetype”field enables categorization of data for improved searching. Forinstance, a source type indicator can be used in searches to find dataof a certain type. In some cases, a sourcetype can be automaticallyassigned to events in accordance with identification of a matching rulepackage. For instance, the field extraction system 1816 may identify andadd a sourcetype field when it identifies a rule package with a highestmatch rate. As a result, an event can include a “sourcetype” field.

As can be appreciated, the rule matching component 1832 can also beconfigured to extract values using a set of one or more extraction rules(e.g., matched extraction rules). A set of extraction rules to apply toan event set may be determined in any number of ways. In some cases, asdiscussed above, the rule matching component 1832 may be utilized todetermine a set of extraction rules (e.g., rule package) to use inassociation with an event set. For example, the events may be comparedto various extraction rules to select a most appropriate extractionrule(s) to use for extraction (e.g., extraction rule with a highestmatch rate). In other cases, a set of extraction rules and correspondingmatch rates may be provided to the user for selection of an extractionrule(s) to apply to an event set. In yet other cases, a user may input aset of extraction rules desired for use in performing data extraction.Upon obtaining or identifying an extraction rule(s) for performing dataextraction, the extraction rule(s) can be applied to a set of events toextract data or fields. Thereafter, in some cases, a match rate can bedetermined (e.g., how many events do not match any extraction rules orhow many rules do not match any events). Matching and/or extractingperformed by the rule matching component 1832 may be triggered based onan input of a set of events for which field extraction is desired.

The rule generating component 1834 is generally configured to generateextraction rules, for example for particular events. In this regard, therule generating component 1834 can generate new extraction rules, orrule packages having extraction rules, that match or correspond withevents. In some cases, the rule generating component 1834 can be used togenerate new rules when existing extraction rules (e.g., rule packages)are not deemed to match a set of events. For example, an existing rulepackage may not be deemed to match an event set if a match rate does notexist above a threshold value (e.g., 50%). In such a case, rulegenerating component 1834 may generate extraction rules applicable tothe particular events. In other cases, the rule generating component1834 may generate rules even when existing extraction rules (e.g., arule package) are deemed to match a set of events. For example, in somecases, upon identifying matches via the rule matching component 1832,the user may select to preview one of the matched rule packages (e.g.,with the highest match rate inferring sourcetype) and also select togenerate additional extraction rules for the events. In yet other cases,the rule generating component 1834 can be used to generate new ruleswhen existing extraction rules are invalid or deficient. For instance,when extraction rules do not match any of the events within a particulartime frame (e.g., five minutes), the rule generating component 1834 maygenerate extraction rules corresponding to the events.

The rule generating component 1834 can generate extraction rules in anynumber of ways. As one example, extraction rules may be generated basedon analysis of the event set. By way of example only, extraction rulesmay be generated by detecting events formats (e.g., JSON, SML, Tabular,Key-value, unstructured, etc.), performing automatic field discovery,and clustering events by machine learning algorithms. More details ofmethods that can be used to generate extraction rules can be found in USPublication Nos. 2017/0286038 and 2017/0286455, which are herebyincorporated by reference. Irrespective of how extraction rules aregenerated, such newly generated extraction rules can be stored in theextraction rule data store 1842 for subsequent use. Accordingly, suchnewly generated extraction rules enhance the available extraction rulesand, as described in more detail below, can be further improved inaccordance with feedback from users.

The rule enhancing component 1836 is generally configured to enhanceextraction rules. In particular, the rule enhancing component 1836facilitates obtaining extraction rule feedback and using such feedbackto enhance extraction rules for subsequent use. In this way, the ruleenhancing component 1836 enables enhancement of extraction rules basedon user feedback, and in some cases, feedback across various tenants ofthe data-processing system 1802.

The rule enhancing component 1836 may obtain user feedback via agraphical user interface presented to a user (e.g., via client device1804). Generally, extraction rules can be previewed to enable userfeedback. Extraction rule preview may be initiated in any number ofways. As one example, upon determining rule packages that match an eventset and/or generation of an extraction rule(s), the rule enhancingcomponent 1836 can provide the matched extraction rules andcorresponding match rates to a user via a graphical user interface. Inaccordance with presenting extraction rules (e.g., rule packages) andcorresponding matching rates, a user may select a particular set ofextraction rules (e.g., rule package) for which to preview. For example,a user may select a rule package associated with a highest match rate.As another example, a set of extraction rules may be previewed based onautomatic selection of extraction rules (e.g., a rule package with ahighest matching score may be automatically previewed).

In providing an extraction rule preview, various types of informationmay be provided. For example, a set of extraction rules may be provided(e.g., a set of extraction rules of a selected rule package). Events mayalso be provided for presentation. For example, in some cases, allevents of the event set may be provided. In other cases, events matchingor corresponding with a particular extraction rule or the rule packagemay be presented. In some cases, the values extracted, or to beextracted, from the events may be visually emphasized (e.g.,highlighted) within the events. Summary information may also be providedwithin a preview. For instance, number of fields, event match rate,number of extractions, number of distinct values, etc. may be determinedand presented to a user.

A user may provide various types of feedback pertaining to theextraction rule preview. By way of example only, feedback may includeextraction rule customization, field name editing, or the like. Forinstance, a user may update a “field 1” name to “host.” The feedbackprovided by a user(s) can be used to enhance extraction rules forsubsequent use. For example, continuing with the example of the “field1” name being updated to “host.” When such feedback is captured, upondetecting a subsequent similar pattern (e.g., a value before an IPaddress), a determination can be made to change the field name to“host.”

In some cases, in addition to providing direct user feedback (e.g., usermodifications), additional context may be captured and used to enhanceextraction rules. Context may refer to any information associated with auser-provided feedback. For example, assume a user modifies a fieldname. In such a case, feedback context may include a time associatedwith the field name modification, position of the field, data or valueswithin a range or distance from the field name modification (e.g.,values in the two previous fields and two following fields), field nameswithin a range or distance from the field name modification (e.g., fieldnames in the two previous fields and two following fields), or the like.

Feedback and corresponding context can be provided to a feedback datastore, such as feedback data store 1844. The recorded feedback andcontext can be used to enhance or refine extraction rules. In this way,as users may not know how to customize extraction rules for a set ofevents, the captured feedback and context can be used to facilitateknowledge transfer to other users. For instance, one user can utilizeknowledge provided by another user with regard to extraction rules forthe same sourcetype.

The rule enhancing component 1836 can use feedback and correspondingcontext in any number of ways to enhance extraction rules (e.g., rulepackage). As one example, machine learning can use feedback and/orfeedback context to reorder, remove, and/or refine extraction rules thatcan then be subsequently used to perform data extraction. This can beperformed in any number of ways. By way of example, feedback can benormalized and similar feedback grouped or clustered. For instance,assume one feedback is to rename a field from “number” to “port” after“ipv4/.” Assume another feedback is to rename a field from “number” to“port” after “ipv4:.” These two sets of similar feedback can be mergedinto one feedback. Thereafter, feedbacks can be ordered by correspondingweights, such as how many different users have provided the samefeedbacks, the frequencies of feedbacks, etc. Further, metadata can beleveraged to adjust weights (e.g., authorized users can have higherweights). For instance, a user known to be an administrator, developer,or data scientist associated with a particular entity(s), correspondinguser feedback may have significantly higher weights than feedbackprovided by other users. Feedbacks and associated weights can beprovided for viewing, for instance, within the extraction rules previewpage. A user may then be able to select a preference or use a default(e.g., with a highest weight).

The rule validating component 1838 is configured to validate whetherextraction rules selected or identified for data extraction are valid orinvalid. A valid extraction rule refers to an extraction rule thatoperates to extract values or fields. On the other hand, an invalidextraction rule refers to an extraction rule that fails to extractvalues or fields.

In validating extraction rules in association with performing dataextraction, the rule validating component 1838 can monitor if anextraction rule(s) being applied to a set of events is effectivelyextracting values. Extraction rule validation can be performed in anynumber of ways. As one example, a set of one or more extraction rules(e.g., a particular extraction rule) may be deemed invalid orineffective when a threshold number of events within an event set do notmatch or correspond with any extraction rule. As another example, a setof extraction rules may be deemed invalid or ineffective when athreshold number of events within an event set do not match orcorrespond with any extraction rule within a particular amount of time(e.g., 5 minutes). As another example, an extraction rule may be deemedinvalid when the extraction rule matches no events or a less ratio ofevents than before. For instance, assume that in last seven days, onerule matches 20% events, but only matches 5% in last 1 hour. In such acase, the rule can be determined to be invalid (e.g., can assume somesample formats changed) and an alert can be sent to an administrator.The administrator can decide if the extraction rule is as designed(removed one appliance from ENV), or whether the extraction rule shouldbe fixed. As can be appreciated, in some implementations, theadministrator can set a threshold (match ratio degradation >5%) ormonitor time range (daily or hourly) to trigger the alert.

In cases that the rule validating component 1838 detects a particularset of extraction rules being applied to an event set is invalid orineffective, the rule validating component 1838 may initiate generationof extraction rules, for example, based on the events. To this end, therule generating component 1834 may be initiated to generate newextraction rules that can be applied to the event set. Such newlygenerated extraction rules can be stored in the extraction rule datastore 1842 for subsequent use.

In some cases, upon detecting an invalid or deficient set of extractionrules, an alert may be provided via a graphical user interface to alertor notify a user of the invalid extraction rules. In this way, uponrecognizing the alert or notification, a user may select to initiate thegeneration of new extraction rules. Such new extraction rules can bestored in extraction rule data store 1842.

As can be appreciated, the data-processing system 1802, or portionsthereof, can be used in accordance with various workflows to performdifferent functionality. As one example, the data processing system 1802can operate to enhance extraction rules via a build-time workflow, whichis described in more detail below. Generally, the build-time workflow isimplemented or used at instances during which extraction rules are beinggenerated and enhanced for subsequent use. As another example, the dataprocessing system 1802 can operate to validate extraction rules via arun-time workflow, which is described in more detail below. Generally,the run-time workflow is implemented or used at instances during whichfield extraction is initiated.

3.2 Extraction Rule Enhancement Via Build-Time Implementation

As previously described, extraction rules, particularly customizedextraction rules, can be difficult to construct with an insufficient setof events to reference. Further, user interfaces can be difficult andtime consuming to operate to create extraction rules. Accordingly,embodiments describe herein are directed to an efficient and effectivemanner of enhancing extraction rules. Generally, and at a high-level,feedback or knowledge pertaining to extraction rules can be accumulatedand used to improve or enhance the set of extraction rules stored oraccessible for subsequent use.

FIG. 19 provides an illustrative implementation 1900 of performingextraction rule enhancement. Implementation 1900 can be used to generateand build extraction rules that can be subsequently used for performingdata extraction. Such an implementation or workflow may be referred toherein as a build-time implementation or workflow. As shown, thebuild-time implementation 1900 can include a data-processing component1930, a rule matching component 1932, a rule generating component 1934,and a rule enhancing component 1936. Such components may be similar tothe corresponding components discussed in reference to FIG. 18 .

As illustrated in FIG. 19 , events 1950 can be input into adata-processing component 1930. The events can generally be any set ofevents. In some cases, the events are events input into data-processingcomponent 1930 at ingest or index time. The data processing component1930 can anonymize data within the events. In one embodiment, the dataprocessing component 1930 is configured to anonymize sensitive orprivate data within the events. For example, using a set of predefinedanonymization rules, sensitive data may be removed or replaced (e.g.,with a default value) within events.

The anonymized events can be input into the rule matching component1932. As shown, the rule matching component 1932 can include or haveaccess to an extraction rule data store 1942 that includes a set of rulepackages. The rule matching component 1932 can identify one or more rulepackages that correspond with or match the events. As previouslydescribed, a rule package generally refers to a particular set ofextraction rules related in some manner (e.g., associated with a samesourcetype). To this end, the rule matching component 1932 matches oneor more rule packages with events. As such, the rule matching component1932 may reference rule packages stored in extraction rule data store1942 and analyze extraction rules within the rule packages to identifyone or more rule packages that correspond with or match an event set.

Identifying a set of rule packages that match or correspond with a setof events can occur in any number of ways. In one implementation, therule matching component 1932 may determine match rates associated withone or more rule packages (e.g., each rule package in the set of rulepackages). A match rate for a rule package indicates an extent,proportion, percentage, or rate at which at least one extraction rule ofa rule package corresponds with, or matches, the events. For example, an88% match rate associated with a first rule package indicates that atleast one extraction rule in a first rule package matches or correspondswith 88% events within a set of events. Accordingly, each rule packagemay be analyzed in light of a set of events to determine a match ratefor the corresponding rule package.

The match rates determined by the rule matching component 1932 can thenbe used to determine one or more extraction rules that match an eventset. For example, rule packages associated with a match rate above athreshold value (e.g., 30%, 50%, 80%, etc.) may be considered a matchwith an event set. As another example, rule packages associated with apredetermined number (e.g., 1, 3, etc.) of highest match rates may bedeemed a match with an event set. As yet another example, a maximumnumber of rule packages (e.g., 3) associated with the highest matchrates and exceeding a threshold value may be deemed a match with anevent set. Rule packages deemed to match an event set, and correspondingmatch rates, can be provided to the rule enhancing component 1934 forcommunication to a user, via a graphical user interface. In some cases,each extraction rule or rule package may be deemed a match.

In the event a rule package is not deemed matching, the rule generatingcomponent 1934 can generate an extraction rule(s) applicable to theevent set. In some cases, a rule generating component may be used togenerate rules even in the event a matching extraction rule isidentified. The rule generating component 1934 can generate extractionrules in any number of ways. As one example, extraction rules may begenerated based on analysis of the event set. Irrespective of howextraction rules are generated, such newly generated extraction rulescan be stored in the extraction rule data store 1942 for subsequent use.

The rule packages identified as matching the events (e.g., via the rulematching component 1932) and/or new generated extraction rules (e.g.,via the rule generating component 1934) can be provided to the ruleenhancing component 1936. The rule enhancing component 1936 is generallyconfigured to enhance extraction rules. In particular, the ruleenhancing component 1936 facilitates obtaining extraction rule feedbackand using such feedback to enhance extraction rules for subsequent use.In this way, the rule enhancing component 1936 enables enhancement ofextraction rules based on user feedback, and in some cases, feedbackacross various tenants of a data-processing system.

The rule enhancing component 1936 may obtain user feedback via agraphical user interface presented to a user. Generally, extractionrules can be previewed to enable user feedback. Extraction rule previewmay be initiated in any number of ways. As one example, upon determiningrule packages that match an event set and/or generation of an extractionrule(s), the rule enhancing component 1936 can provide the matchedextraction rules and corresponding match rates and/or newly generatedextraction rules (and, in some cases, corresponding match rates) to auser via a graphical user interface. In accordance with presenting rulepackages and/or extraction rules and corresponding matching rates, auser may select a particular set of extraction rules (e.g., rulepackage) for which to preview. For example, a user may select a rulepackage associated with a highest match rate. As another example, a setof extraction rules may be previewed based on automatic selection ofextraction rules (e.g., a rule package with a highest matching score maybe automatically previewed).

In providing an extraction rule preview, various types of informationmay be provided. For example, a set of extraction rules of a selectedrule package may be provided. Additionally, events matching orcorresponding with the selected rule package may be presented. In somecases, the values extracted, or to be extracted, from the events may bevisually emphasized (e.g., highlighted) within the events. Summaryinformation may also be provided within a preview. For instance, numberof fields, event match rate, number of extractions, number of distinctvalues, etc. may be determined and presented to a user.

The rule enhancing component 1936 may obtain various types of feedbackpertaining to the extraction rule preview (e.g., provided via a user).By way of example only, feedback may include extraction rulecustomization, field name editing, or the like. For instance, a user mayupdate a “field 1” name to “host.” The feedback provided by a user(s)can be used to enhance extraction rules for subsequent use. In somecases, in addition to obtaining direct user feedback (e.g., usermodifications), additional context may be obtained or identified via therule enhancing component 1936 and used to enhance extraction rules. Asdescribed, context may refer to any information associated with auser-provided feedback. For example, assume a user modifies a fieldname. In such a case, feedback context may include a time associatedwith the field name modification, position of the field, data or valueswithin a range or distance from the field name modification (e.g.,values in the two previous fields and two following fields), field nameswithin a range or distance from the field name modification (e.g., fieldnames in the two previous fields and two following fields).

Feedback and corresponding context can be stored in feedback data store1944. The recorded feedback and context can be used to enhance or refineextraction rules. In this way, the rule enhancing component 1936 canutilize the captured feedback and context to enhance extraction rules,thereby facilitating knowledge transfer for subsequent use (e.g., byother users). The rule enhancing component 1936 can use feedback andcorresponding context in any number of ways to enhance extraction rules(e.g., rule package). As one example, machine learning can be used toreorder, remove, and/or refine extraction rules that can then besubsequently used to perform data extraction.

The enhanced extraction rules can be stored in the extraction rule datastore 1942. As such, the enhanced extraction rules in the extractionrule data store 1942 can be used as a basis for further enhancement, forexample, upon analyzing a different event set. As can be appreciated,the enhanced extraction rules can additionally or alternatively beaccessed and used to perform data extraction. In this way, users canbenefit from the enhanced extraction rule to appropriately extractfields from events.

In accordance with implementations described herein, FIGS. 20A-20Hdepict illustrative user interfaces that may be used to facilitateenhancement of extraction rules. As described, a user can interact withsuch interfaces via various input or interaction mechanisms. Beginningwith FIG. 20A, FIG. 20A depicts an example user interface for initiatingextraction rule enhancement. In particular, as shown in user interface2000, a user may select to upload sample data or events 2002 titled“sample.txt.” In accordance with selecting a set of events, the events2004 can be presented.

Upon selecting data or events for which to enhance extraction rules, auser may select field settings icon 2006 of FIG. 20B to initiate dataanonymization. In some cases, upon selecting to anonymize data,anonymization may automatically occur, for example, using defaultanonymization rules. In other embodiments, a user interface 2008 of FIG.20C may be utilized to select anonymization options, such as specificanonymization rules to apply. For example, a list of anonymization rules2010 can be presented for a user to view, edit, and/or apply to theevents. Anonymization rules 2100 can be stored, for example, inassociation with extraction rule data store (e.g., extraction rule datastore 1842). Advantageously, and by way of example, a customizedanonymization rule to anonymize IPv6 can be accessed and leveraged todiscover fields (e.g., via a rule generating component 1834).

Upon anonymizing data, the events can be analyzed in light of variousrule packages to determine match rates associated with the rulepackages. Thereafter, a user can be presented with rule packages andcorresponding match rates. As shown in FIG. 20D, an indication of afirst rule package 2012 and corresponding match rate 2014, an indicationof a second rule package 2016 and corresponding match rate 2018, and anindication of a third rule package 2020 and corresponding match rate2022 are presented. In cases that rule packages are associated with asourcetype, in some embodiments, the sourcetype may be presented as theindication of the rule package, as illustrated in FIG. 20D. A user mayselect one of the rule packages, or sourcetypes, to preview.Alternatively or additionally to a user selecting a rule package forpreview, a user may select to generate extraction rules via generateicon 2024 of FIG. 20E.

A preview of a set of extraction rules can be presented to a user. Forexample, assume a user selects the first rule package 2012 of FIG. 20Dfor preview. In such a case, a preview of the extraction rules can beprovided, as illustrated in FIG. 20F. As shown, a summary portion 2026may be presented with various types of information, such as number offields, event match rate, number of extractions, and number of distinctvalues. An extraction rule portion 2028 provides indications of theextraction rules of the selected rule package. For example, extractionrule portion 2028 includes a first extraction rule that is applicable to615 events of a total 1000 events, a second extraction rule that isapplicable to 145 events, a third extraction rule that is applicable to140 events, and a fourth extraction rule that is applicable to 100events. Each extraction rule can be selected to present correspondingdata. For example, if the first extraction rule is selected, informationassociated therewith can be presented (e.g., extraction rule, fields,events, or the like).

In accordance with previewing a set of extraction rules, a user mayprovide feedback in relation to the extraction rule(s). For example, asillustrated in FIG. 20G, a user may select to deactivate 2040, edit2042, or delete 2044 a field or field name. A user may also select toobtain recommendations, such as new field name recommendations. Forinstance, in FIG. 20H, field name recommendation 2050, field namerecommendation 2052, and field name recommendation 2054 can be providedas recommendations. A user may select one of the name recommendations tomodify a field name and provide feedback for enhancing extraction rules.

Turning to FIG. 21 , FIG. 21 illustrates a method 2100 of enhancingextraction rules, in accordance with embodiments of the presentinvention. As can be appreciated, additional or alternative steps mayalso be included in different embodiments. Such a method 2100 may beperformed, for example, at a field extraction system, such as fieldextraction system 1816 of FIG. 18 .

Initially, at block 2102, a set of events is obtained. Such a set ofevents may be obtained, for example, at ingest time, index time, orsearch time. Data within the set of events can be anonymized, as shownat block 2104. At block 2106, a determination is made as to whether arule package matches the set of events. As described, such adetermination may occur in any number of ways, such as whether an extentof which at least one extraction rule in a rule package matches theevent set exceeds a threshold. If so, a rule package, or set of rulepackages, can be presented to a user, as indicated at block 2108. Insome cases, the rule package(s) may be presented with the correspondingmatch rate. On the other hand, if it is determined that a rule packagedoes not match the set of events, at block 2110, an extraction rule(s)is generated in association with the event set.

At block 2112, a selection is received to preview an extraction rule.Such a selection may be made in accordance with the presented matchingrule packages or the newly generated extraction rule. Thereafter, atblock 2114, the extraction rule and events matching the extraction ruleare presented. A modification to the extraction rule and/or event datais received at block 2116. Thereafter, at block 2118, the modificationis used to enhance extraction rules available for performing subsequentdata extraction. Enhancing the extraction rules can occur in any numberof ways including, for example, using machine learning to reorderextraction rules, replace extraction rules, modify extraction rules, orthe like.

3.3 Extraction Rule Validation and Enhancement Via Run-TimeImplementation

Extraction rules are not always effective for a particular set ofevents. Oftentimes, however, a user is unaware of ineffective extractionrules during field extraction. Further, it can be difficult and timeconsuming for a user to attempt to “fix” an extraction rule.Accordingly, embodiments describe herein are directed to an efficientand effective manner of validating and enhancing extraction rules,particularly while performing data or field extraction. Generally, andat a high-level, extraction rules can be monitored as applied to a setof events in an effort to extract data. In cases that an extractionrule(s) is deemed invalid, a new extraction rule(s) can be generated(e.g., automatically or based on a user selection). Such a newextraction rule can be used to improve or enhance the set of extractionrules stored or accessible for subsequent use.

FIG. 22 provides an illustrative implementation 2200 of facilitatingvalidation and enhancement of extraction rules. Implementation 2200 canbe used to monitor and, if needed, generate extraction rules that can besubsequently used for performing data extraction. Such an implementationor workflow may be referred to herein as a run-time implementation orworkflow. As shown, the run-time implementation 2200 can include a rulematching component 2232, a rule generating component 2234, and a rulevalidating component 2238. Such components may be similar to thecorresponding components discussed in reference to FIG. 18 .

As illustrated in FIG. 22 , events 2250 can be input into rule matchingcomponent 2232. The input events 2250 can generally be any set ofevents. In some cases, the events are events input at ingest, index, orsearch time. The rule matching component 2232 can facilitateidentification of one or more extraction rules that correspond with ormatch the events. As such, the rule matching component 2232 matches oneor more extraction rules with events. In this way, the rule matchingcomponent 2232 may reference extraction rules stored in extraction ruledata store and analyze extraction rules to identify one or moreextraction rules that correspond with or match an event set.

Identifying extraction rules that match or correspond with a set ofevents can occur in any number of ways. In one implementation, the rulematching component 2232 may determine match rates associated with one ormore extraction rules (e.g., rule packages). The match rates determinedby the rule matching component 2232 can then be used to determine one ormore extraction rules that match an event set. For example, anextraction rule(s) (e.g., rule packages) associated with a highest matchrate may be considered a match with input events 2250. In some cases,extraction rules deemed to match an event set, and corresponding matchrates, can be provided to a user, via a graphical user interface, forselection or confirmation by the user to use the extraction rules fordata extraction. In other cases, the extraction rule(s) deemed to matchan event set may be automatically identified for application to theevent set 2250 to extract data or fields.

Although implementation 2200 is shown using a rule matching component2232 by matching extraction rules to events, in additional oralternative embodiments, extraction rules can be identified in othermanners. For example, in some cases, a user may select or input anextraction rule for use in extraction data.

Upon identifying extraction rules to apply for data extraction, the rulematching component 2232 can utilize the identified extraction rules toextract data, or fields, from the event set 2250. In accordance withrule matching component 2232 performing data extraction, or attemptingto extract data, the rule validating component 2238 can identify if anextraction rule, such as a current extraction rule, is valid. In thisregard, the rule validating component 2238 may determine an extractionrule is invalid in cases in which the extraction rule cannot match anyevents (e.g., of the event set 2250). In cases in which an extractionrule(s) is determined to be invalid, the rule generating component 2234can generate a new extraction rule(s) for application to the event set2250. As can be appreciated, the new extraction rule(s) can be appliedto the current event set 2250 and/or stored for subsequent use.

In some cases, prior to the rule generating component 2234 generating anew extraction rule(s), an alert or notification can be provided to auser to indicate an invalid extraction rule. The user may also beprovided with an option to generate new extraction rules. Upon selectionto generate new extraction rules, the rule generating component 2234 canoperate to generate a new extraction rule(s).

FIG. 23 illustrates a method of validating and enhancing extractionrules, in accordance with embodiments of the present invention. As canbe appreciated, additional or alternative steps may also be included indifferent embodiments. Such a method 2300 may be performed, for example,at a field extraction system, such as field extraction system 1816 ofFIG. 18 .

Initially, at block 2302, a set of events are obtained. Such a set ofevents may be obtained, for example, at ingest time, index time, orsearch time. At block 2304, an extraction rule(s) is identified to applyto the set of events. An extraction rule(s) to apply to a set of eventscan be identified in any number of ways. For example, a rule matchingcomponent may be used to identify an extraction rule(s) or rulepackage(s) that matches the events. As another example, an extractionrule(s) to apply to a set of inputs may be selected or input by a user.At block 2306, the identified extraction rule(s) is applied to the setof events. In accordance with the application of the extraction rule(s),at block 2308, the application of the extraction rule is monitored todetermine if an extraction rule is invalid. For example, if anextraction rule does not result in any matches with events, theextraction rule can be deemed invalid. In cases that the extraction ruleis deemed invalid, at block 2310, a new extraction rule(s) can begenerated in association with the set of events and returned to block2306 for application to the events.

3.4 Illustrative Hardware System

The systems and methods described above may be implemented in a numberof ways. One such implementation includes computer devices havingvarious electronic components. For example, components of the system inFIG. 18 may, individually or collectively, be implemented with deviceshaving one or more Application Specific Integrated Circuits (ASICs)adapted to perform some or all of the applicable functions in hardware.Alternatively, the functions may be performed by one or more otherprocessing units (or cores), on one or more integrated circuits orprocessors in programmed computers. In other embodiments, other types ofintegrated circuits may be used (e.g., Structured/Platform ASICs, FieldProgrammable Gate Arrays (FPGAs), and other Semi-Custom ICs), which maybe programmed in any manner known in the art. The functions of each unitmay also be implemented, in whole or in part, with instructions embodiedin a memory, formatted to be executed by one or more general orapplication-specific computer processors.

An example operating environment in which embodiments of the presentinvention may be implemented is described below in order to provide ageneral context for various aspects of the present invention. Referringto FIG. 24 , an illustrative operating environment for implementingembodiments of the present invention is shown and designated generallyas computing device 2400. Computing device 2400 is but one example of asuitable operating environment and is not intended to suggest anylimitation as to the scope of use or functionality of the invention.Neither should the computing device 2400 be interpreted as having anydependency or requirement relating to any one or combination ofcomponents illustrated.

The invention may be described in the general context of computer codeor machine-useable instructions, including computer-executableinstructions such as program modules, being executed by a computer orother machine, such as a personal data assistant or other handhelddevice. Generally, program modules including routines, programs,objects, components, data structures, etc., refer to code that performparticular tasks or implement particular abstract data types. Theinvention may be practiced in a variety of system configurations,including handheld devices, consumer electronics, general-purposecomputers, more specialized computing devices, etc. The invention mayalso be practiced in distributed computing environments where tasks areperformed by remote-processing devices that are linked through acommunications network.

With reference to FIG. 24 , computing device 2400 includes a bus 2410that directly or indirectly couples the following devices: memory 2412,one or more processors 2414, one or more presentation components 2416,input/output (I/O) ports 2418, I/O components 2420, and an illustrativepower supply 2422. Bus 2410 represents what may be one or more busses(such as, for example, an address bus, data bus, or combinationthereof). Although depicted in FIG. 24 , for the sake of clarity, asdelineated boxes that depict groups of devices without overlap betweenthese groups of devices, in reality, this delineation is not so clearcut and a device may well fall within multiple ones of these depictedboxes. For example, one may consider a display to be one of the one ormore presentation components 2416 while also being one of the I/Ocomponents 2420. As another example, processors have memory integratedtherewith in the form of cache; however, there is no overlap depictedbetween the one or more processors 2414 and the memory 2412. A person ofskill in the art will readily recognize that such is the nature of theart, and it is reiterated that the diagram of FIG. 24 merely depicts anillustrative computing device that can be used in connection with one ormore embodiments of the present invention. It should also be noticedthat distinction is not made between such categories as “workstation,”“server,” “laptop,” “handheld device,” etc., as all such devices arecontemplated to be within the scope of computing device 2400 of FIG. 24and any other reference to “computing device,” unless the contextclearly indicates otherwise.

Computing device 2400 typically includes a variety of computer-readablemedia. Computer-readable media can be any available media that can beaccessed by computing device 2400 and includes both volatile andnonvolatile media, and removable and non-removable media. By way ofexample, and not limitation, computer-readable media may comprisecomputer storage media and communication media. Computer storage mediaincludes both volatile and nonvolatile, removable and non-removablemedia implemented in any method or technology for storage of informationsuch as computer-readable instructions, data structures, programmodules, or other data. Computer storage media includes, but is notlimited to, RAM, ROM, EEPROM, flash memory or other memory technology,CD-ROM, digital versatile disks (DVD) or other optical disk storage,magnetic cassettes, magnetic tape, magnetic disk storage or othermagnetic storage devices, or any other medium which can be used to storethe desired information and which can be accessed by computing device2400. Computer storage media does not comprise signals per se, such as,for example, a carrier wave. Communication media typically embodiescomputer-readable instructions, data structures, program modules, orother data in a modulated data signal such as a carrier wave or othertransport mechanism and includes any information delivery media. Theterm “modulated data signal” means a signal that has one or more of itscharacteristics set or changed in such a manner as to encode informationin the signal. By way of example, and not limitation, communicationmedia includes wired media such as a wired network or direct-wiredconnection, and wireless media such as acoustic, RF, infrared, and otherwireless media. Combinations of any of the above should also be includedwithin the scope of computer-readable media.

Memory 2412 includes computer storage media in the form of volatileand/or nonvolatile memory. The memory may be removable, non-removable,or a combination thereof. Typical hardware devices may include, forexample, solid-state memory, hard drives, optical-disc drives, etc.Computing device 2400 includes one or more processors 2414 that readdata from various entities such as memory 2412 or I/O components 2420.Presentation component(s) 2416 present data indications to a user orother device. Illustrative presentation components include a displaydevice, speaker, printing component, vibrating component, etc.

I/O ports 2418 allow computing device 2400 to be logically coupled toother devices including I/O components 2420, some of which may be builtin. Illustrative components include a keyboard, mouse, microphone,joystick, game pad, satellite dish, scanner, printer, wireless device,etc. The I/O components 2420 may provide a natural user interface (NUI)that processes air gestures, voice, or other physiological inputsgenerated by a user. In some instances, inputs may be transmitted to anappropriate network element for further processing. An NUI may implementany combination of speech recognition, stylus recognition, facialrecognition, biometric recognition, gesture recognition both on screenand adjacent to the screen, air gestures, head and eye tracking, andtouch recognition (as described elsewhere herein) associated with adisplay of the computing device 2400. The computing device 2400 may beequipped with depth cameras, such as stereoscopic camera systems,infrared camera systems, RGB camera systems, touchscreen technology, andcombinations of these, for gesture detection and recognition.Additionally, the computing device 2400 may be equipped withaccelerometers or gyroscopes that enable detection of motion.

As can be understood, implementations of the present disclosure providefor various approaches to relating data. The present invention has beendescribed in relation to particular embodiments, which are intended inall respects to be illustrative rather than restrictive. Alternativeembodiments will become apparent to those of ordinary skill in the artto which the present invention pertains without departing from itsscope.

From the foregoing, it will be seen that this invention is one welladapted to attain all the ends and objects set forth above, togetherwith other advantages which are obvious and inherent to the system andmethod. It will be understood that certain features and subcombinationsare of utility and may be employed without reference to other featuresand subcombinations. This is contemplated by and is within the scope ofthe claims.

What is claimed is:
 1. A computer-implemented method comprising:providing for display, via a graphical user interface, a plurality ofextraction rules relevant to an event set and corresponding match rates,the plurality of extraction rules identified as relevant to the eventset by determining a match rate for each extraction rule indicating anumber of events of in the event set that match the extraction rule ascompared to a total number of events in the event set, wherein eachevent in the event set is associated with a timestamp and includes aportion of raw machine data that reflects activity in an informationtechnology environment and that is produced by a component of thatinformation technology environment, and wherein each extraction rule, ofthe plurality of extraction rules, indicates how to extract a subportionof text from the portion of raw machine data in the event to produce avalue for a field specified by the extraction rule; receiving, via thegraphical user interface, a selection of an extraction rule of theplurality of extraction rules; providing for display, via the graphicaluser interface, a set of events matching the selected extraction rule;receiving, via the graphical user interface, a modification applied tothe displayed extraction rule and a modification applied to a field nameassociated with the set of events matching the selected extraction rule;and providing the modifications, provided via the graphical userinterface, into a machine learning model to enhance extraction rulesavailable for performing subsequent data extraction, wherein the machinelearning model uses the modifications to enhance the extraction rules byreordering extraction rules.
 2. The computer-implemented method of claim1 further comprising: obtaining the event set; and anonymizing at leasta portion of data in the event set.
 3. The computer-implemented methodof claim 1 further comprising anonymizing at least a portion of data inthe event set by replacing the at least the portion of the data with oneor more default values.
 4. The computer-implemented method of claim 1,wherein the plurality of extraction rules identified as relevant isbased on the corresponding match rates exceeding a threshold.
 5. Thecomputer-implemented method of claim 1 further comprising determiningthe plurality of extraction rules relevant to the event set by comparingextraction rules to the event set.
 6. The computer-implemented method ofclaim 1 wherein the plurality of extraction rules identified as relevantcorrespond with high match rates.
 7. The computer-implemented method ofclaim 1, wherein the set of events matching the selected extraction ruleare presented with values extracted via the selected extraction rulebeing visually emphasized within the set of events.
 8. Thecomputer-implemented method of claim 1, further comprising receiving amodification of a field value.
 9. The computer-implemented method ofclaim 1, wherein the machine learning model further uses themodifications to enhance the extractions rules by replacing extractionrules or refining extraction rules.
 10. The computer-implemented methodof claim 1 further comprising using at least a portion of the enhancedextraction rules to perform data extraction.
 11. Thecomputer-implemented method of claim 1 further comprising: identifyingcontext associated with the modification applied to the displayedextraction rule; and providing the context into the machine learningmodel to generate the enhanced extraction rules.
 12. One or morecomputer storage media having instructions stored thereon, wherein theinstructions, when executed by a computing device, cause the computingdevice to: provide for display, via a graphical user interface, aplurality of extraction rules relevant to an event set and correspondingmatch rates, the plurality of extraction rules identified as relevant tothe event set by determining a match rate for each extraction ruleindicating a number of events of in the event set that match theextraction rule as compared to a total number of events in the eventset, wherein each event in the event set is associated with a timestampand includes a portion of raw machine data that reflects activity in aninformation technology environment and that is produced by a componentof that information technology environment, and wherein each extractionrule, of the plurality of extraction rules, indicates how to extract asubportion of text from the portion of raw machine data in the event toproduce a value for a field specified by the extraction rule; receive,via the graphical user interface, a selection of an extraction rule ofthe plurality of extraction rules; provide for display, via thegraphical user interface, a set of events matching the selectedextraction rule; receive, via the graphical user interface, amodification applied to the displayed extraction rule and a modificationapplied to a field name associated with the set of events matching theselected extraction rule; and provide the modifications, provided viathe graphical user interface, into a machine learning model to enhanceextraction rules available for performing subsequent data extraction,wherein the machine learning model uses the modifications to enhance theextraction rules by reordering extraction rules.
 13. The computerstorage media of claim 12 further causing the computing device to:obtain the event set; and anonymize at least a portion of data in theevent set.
 14. The computer storage media of claim 12 further causingthe computing device to anonymize at least a portion of data in theevent set by replacing the at least the portion of the data with one ormore default values.
 15. The computer storage media of claim 12 furthercausing the computing device to determine the plurality of extractionrules relevant to the event set by comparing extraction rules to theevent set.
 16. The computer storage media of claim 12, wherein theplurality of extraction rules identified as relevant correspond withhigh match rates.
 17. The computer storage media of claim 12, whereinthe set of events matching the selected extraction rule are presentedwith values extracted via the selected extraction rule being visuallyemphasized within the set of events.
 18. A computing system comprising:one or more processors; and a memory coupled with the one or moreprocessors, the memory having instructions stored thereon, wherein theinstructions, when executed by the one or more processors, cause thecomputing system to: provide for display, via a graphical userinterface, a plurality of extraction rules relevant to an event set andcorresponding match rates, the plurality of extraction rules identifiedas relevant to the event set by determining a match rate for eachextraction rule indicating a number of events of in the event set thatmatch the extraction rule as compared to a total number of events in theevent set, wherein each event in the event set is associated with atimestamp and includes a portion of raw machine data that reflectsactivity in an information technology environment and that is producedby a component of that information technology environment, and whereineach extraction rule, of the plurality of extraction rules, indicateshow to extract a subportion of text from the portion of raw machine datain the event to produce a value for a field specified by the extractionrule; receive, via the graphical user interface, a selection of anextraction rule of the plurality of extraction rules; provide fordisplay, via the graphical user interface, a set of events matching theselected extraction rule; receive, via the graphical user interface, amodification applied to the displayed extraction rule and a modificationapplied to a field name associated with the set of events matching theselected extraction rule; and provide the modifications, provided viathe graphical user interface, into a machine learning model to enhanceextraction rules available for performing subsequent data extraction,wherein the machine learning model uses the modifications to enhance theextraction rules by reordering extraction rules.
 19. The system of claim18, further comprising receiving a modification of a field value. 20.The system of claim 18, wherein the machine learning model further usesthe modifications to enhance the extractions rules by replacingextraction rules or refining extraction rules.
 21. The system of claim18 further comprising using at least a portion of the enhancedextraction rules to perform data extraction.
 22. The system of claim 18further comprising: identifying context associated with the modificationto the displayed extraction rule; and providing the context into themachine learning model to generate the enhanced extraction rules.